Ecommerce and marketplaces
A Pantera digital worker breaks every payout back down into the orders behind it, matches it against what the ERP recorded, and escalates only the differences that are real — across every gateway, marketplace and bank account you sell through.
Written for CFOs, controllers and finance leads at ecommerce operations in Colombia and Mexico.
Why this breaks
A gateway or a marketplace does not deposit what the customer paid. It deposits a netted batch, on its own cycle, after deducting commissions, withholdings, refunds and whatever it decided to hold back — and your ERP recorded the gross sale on a different day.
One deposit, hundreds of orders
A single transfer can cover three days of sales across several payment methods. Opening it up order by order is the only way to know whether it is right, and it is the first thing a busy team stops doing.
Refunds and chargebacks move backwards
A return filed this month reduces a payout next month, often without the credit note being issued. The books show revenue that the bank already took back.
Every channel has its own report
Each gateway and each marketplace publishes settlements in its own format, on its own schedule, with its own names for the same deduction. Someone downloads them all and pastes them into a spreadsheet.
Shipping is billed in bulk, long after the sale
Couriers invoice hundreds of shipments at once, weeks later. Tying that invoice back to the orders it delivered is what makes the real margin per order so hard to see.
What it runs
Volume is the whole problem. Each order is small, each deduction is small, and there are thousands of them — which is exactly the shape of work a digital worker is for.
Payouts broken back down into orders
Each settlement report is read the same way a bank statement is read: the payout is split back into the orders, commissions, withholdings and adjustments it contains, matched against the ERP and against the bank, and anything left over is escalated with the evidence attached.
Refunds, chargebacks and credit notes
Money that moves backwards is tied to the order it came from and to the document that should support it, so a return does not sit in the books as revenue you no longer have.
Courier and supplier invoices
Bulk shipping invoices are checked line by line against what was actually sent, and supplier invoices against their purchase orders, before anything is posted. Only genuine exceptions reach a person.
Electronic invoicing compliance
Documents are validated against the tax authority before they enter the books — CFDI against the SAT in Mexico, electronic invoices under DIAN rules in Colombia — so a bad document does not surface during the close.
Every channel stays visible on its own
Differences are reported per gateway and per marketplace, not as one consolidated number, so a channel whose deductions are creeping up shows itself instead of disappearing into the total.
On your own systems
The digital worker works inside the ERP you already run — Siesa, SAP Business One, Siigo, Contpaqi or Aspel — and reads each channel's reports the way your team reads them today, with read-only access.
Your rules, not ours
The matching criteria are the ones your controller already applies by hand. You show them once and the digital worker runs them from then on, the same way every day.
Everything it does is evidence
Every action, every rule applied and every approval is recorded with its audit trail, so a difference can be explained months later without reconstructing it from memory.
Next step
Thirty minutes, on an ERP like yours. Pick the gateway or marketplace that takes your team the longest to reconcile and we will show you what it looks like when a digital worker owns it.
AI digital workers that execute finance operations on the systems you already run.
Backed by
Product
Offices
Fort Lauderdale, United States
Mexico City, Mexico
Bogotá and Medellín, Colombia