A real estate brokerage can have enough money in its bank account, an approved commission statement, and an agent with verified banking details.
And still fail to send the payment.
Not because eCommission is down. Not because the agent entered the wrong routing number.
Sometimes the person trying to release the money simply doesn’t have permission.
That’s one of the more revealing details in eCommission’s integration with CORE BackOffice. The payment system doesn’t treat every office administrator as somebody who should be allowed to move money.
Good. It shouldn’t.
But the actual workflow has a few restrictions that brokerage owners ought to understand before promising agents a faster payday.
Your Office Manager Might Not Have the Right Button
CORE BackOffice separates ordinary administrative access from the authority to initiate eCommission payments.
A broker or super administrator must explicitly enable the permission called:
Allow user to pay agents & vendors via Payment Gateway
It’s managed under My Account → Staff Users.
Without that permission, a staff member can have responsibilities within the brokerage without being authorized to send ACH transfers.
There’s another permission for authorizing eCommission Commission Advances. That one is separate.
This is important because the two products handle different financial arrangements.
Commission Advance involves assigning part of an expected future commission. Payment Gateway handles electronic disbursements after the brokerage has money available to pay.
An employee authorized to approve advances shouldn’t automatically have authority to initiate bank transfers, or vice versa.
The distinction makes sense.
What I’d question is whether a brokerage has actually reviewed these permissions before rolling out the service.
Giving every administrator access to the payment button is convenient right up until someone sends money they weren’t supposed to send.
There’s a Five-Minute Clock on the Payment Screen
The documented CORE BackOffice workflow is surprisingly specific.
After the commission disbursement has been created, an authorized user opens the transaction’s Pay Agent tab and selects $Pay Agent – Payment Gateway.
A five-minute countdown begins.
The person sending the payment selects the brokerage funding source, checks the delivery speed, reviews who will pay any expedited fee, and confirms the transaction.
Then comes two-factor authentication.
The payment isn’t initiated until that verification step is completed.
I can appreciate the security logic. A financial operation shouldn’t sit open indefinitely in an unattended browser.
But this also means the payment screen isn’t a place to start figuring out which account should fund the transfer or who agreed to cover the delivery fee.
Those decisions should already be settled.
If somebody is juggling multiple agent payments, discovering missing information in the middle of a timed authorization process is an excellent way to waste an afternoon.
A $50,000 Commission Isn’t One Transfer
Here’s the restriction that would get my attention as a brokerage owner.
In the documented integration, individual agent transfers have a $50,000 maximum.
Payments below $5 aren’t supported.
And amounts from $5 through $100 can use only the three-business-day delivery option.
For larger commissions, the $50,000 ceiling creates an extra step.
CORE BackOffice documents a workaround that lets the brokerage split a commission disbursement into separate payment entries for the same agent.
For example, a $73,000 payout can be divided into a $50,000 transfer and a $23,000 transfer.
That solves the transfer-limit problem.
But now there are two bank transfers instead of one.
And if the brokerage chooses expedited delivery, the service fee applies to each transfer separately.
At the documented $25 same-day rate, two transfers mean $50 in expedited fees.
The agent may receive one commission statement, but the payment processor sees two separate disbursements.
It’s a small operational distinction with a real financial consequence.
The Expedited Fee Can Come Out of Two Different Pockets
This is one feature I genuinely appreciate.
The brokerage can decide whether it or the agent pays the fee for faster delivery.
Consider a $4,000 commission payment using same-day delivery.
If the agent pays the $25 fee, the agent receives $3,975.
If the brokerage pays it, the agent receives the full $4,000, while the brokerage’s bank account is charged $4,025.
The system allows the payment speed and fee responsibility to be reviewed during the disbursement process.
But there is a frustrating restriction.
If those details need changing after the disbursement has already been created, the documented procedure may require deleting the disbursement, updating the transaction information, and creating it again.
That’s not exactly a graceful editing experience.
I’d want office staff to verify the fee arrangement before generating payment records, especially if the brokerage routinely covers expedited delivery for high-producing agents.
Otherwise, an innocent change can turn into unnecessary rework.
The Approval Problem Nobody Wants to Discover at Closing
CORE BackOffice also supports brokerages where agents prepare their own commission disbursements for approval.
In that arrangement, the agent creates the disbursement, and the broker reviews it.
The agent can’t generate the approved PDF until the brokerage authorizes the document.
Once approved, the agent can no longer freely edit the transaction or disbursement.
If something needs changing, the brokerage must delete the approved disbursement so the agent can correct the information.
That’s understandable from a financial-control perspective.
You don’t want someone changing a commission amount after it has been authorized.
But it creates an obvious operational headache when a last-minute credit, fee, or split adjustment comes through.
The approval process is doing its job. The transaction just needs another round of work.
And this is why I wouldn’t confuse a commission being calculated with a commission being ready for ACH.
There can be document approval, banking verification, funding-account setup, and final payment authorization between those two events.
What About Paying Hundreds of Agents at Once?
This is the question I’d ask eCommission before signing up a large brokerage.
The company markets Payment Gateway as a way to reduce manual commission-payment work.
And CORE BackOffice documents a practical process for initiating payments from individual transactions.
But the public instructions I reviewed do not establish a universal bulk-payment feature where a brokerage selects 200 approved commissions and sends them all through one authorization.
The documented process is transaction-based.
It also explicitly excludes initiating Payment Gateway ACH transfers directly from the Other Income Log.
That doesn’t prove bulk processing is impossible in every eCommission integration.
It means a brokerage should ask for a demonstration of its specific workflow rather than assuming large-scale batch disbursement is included.
For an office with 15 agents, individual transaction payments may be perfectly manageable.
For an organization processing hundreds of commission payments every month, the number of approvals, authentication steps, and transfer records becomes much more important.
The Banking Setup Can Delay the Entire Office
There’s one last dependency worth mentioning.
The brokerage must have an active eCommission funding account before agents can complete their payment setup.
Instant Bank Verification can unlock faster delivery options.
Manual verification remains available, but the documented standard transfer time becomes three business days instead of two.
And the account itself must pass review.
So a brokerage that promises same-day payments before finishing its own bank verification is getting ahead of itself.
The advertised delivery speed is only meaningful when the funding account, recipient account, authorization permissions, and payment cutoff all line up.
Paying Agents Should Be Boring
That’s ultimately what I’d want from eCommission Payment Gateway.
Not another impressive financial dashboard. Not a dozen payment-speed options that nobody understands.
I want the brokerage to know which commissions are approved, which agents have verified accounts, which employees can release payments, and exactly how much money will leave the funding account.
I also want large commissions handled without unexpected fee surprises.
eCommission’s CORE BackOffice integration provides meaningful controls over those steps. The permissions, verification requirements, transfer limits, and fee settings are documented rather than left entirely to guesswork.
But those controls also introduce work.
The software can move money faster. It cannot compensate for a brokerage that hasn’t organized who is allowed to move it.
And when an agent asks why a commission hasn’t arrived, the answer may have very little to do with the bank.
