Reconciliation
How to Reconcile
There are three levels worth reconciling separately:
| Level | What you reconcile | Usual matching key |
|---|---|---|
| Sales | That each sale recorded on your platform has its corresponding payment, for the expected amount | Your own order or sale reference |
| Transaction | That each transaction exists at Getnet with its distribution: each seller's amount and the platform commission | Payment identifier plus seller identifier |
| Bank | That the credit received in the account matches the sum of the settled amounts minus the period's deductions | Settlement identifier and date |
There are also three ways to resolve it, depending on how much automation you want to take on:
| Path | When it makes sense | Status |
|---|---|---|
| Statement API | You want to integrate reconciliation into your own ERP or back office | Available |
| Portal Minha Conta (Getnet's self-service portal) | You prefer to reconcile on screen, without technical integration | Planned for Q4 2026 |
| Integrated reconcilers | You prefer to delegate reconciliation to a specialized service | Available (Beta) |
Statement API
How the Schedule Is Generated
Understanding how the financial schedule is built prevents most closing differences:
- The schedule is generated per item, not per transaction: a sale with several items produces several schedule records and, in the normal payment flow, one record per installment.
- The statement shows what was applied to the sale: if you changed the seller's commission percentage or payment plan on the transaction itself, the statement reflects that value, not the one configured at onboarding.
- Release happens item by item, so a single order may be partially released.
- The MDR (Merchant Discount Rate) and the product fee are fully deducted from the platform's schedule, and the platform commission is paid according to the seller's payment plan.
- Shipping is treated as a sale item, on which you may or may not apply commission.
- In case of cancellation, the MDR paid by the platform is refunded and the commission proportional to the canceled amount is debited.
Recommended Reconciliation Flow
The recommended functional flow, at a high level, follows five steps:
- Daily download by schedule date: brings into the platform's system everything generated in the period, with the breakdown by seller and their commissions.
- Bank-level reconciliation by settlement date: groups the movements by the settlement reference number, checking that the settlement (payouts, commissions, adjustments, chargebacks, and cancellations) matches the credit received in the account.
- Drill down to transaction level, only when there are differences: the detail explains, item by item, what was scheduled, what was released, under which payment plan, and with which commission applied.
- Match against the platform's sales: use the order number and the item code, identifiers sent in the transaction, to connect the statement to the management system.
- Record the identifier of each schedule and each settlement: avoids duplicates when reprocessing a period and lets you query by order to resolve exceptions.
Tip: Before escalating a difference, review these five common causes: rejected payments (for example, due to an error in the bank account details), payments that expired because they were not released within the plan's deadline, transactions sent with a payment plan not contracted at onboarding, orders with items not yet released, and orders with partially canceled items.
Other Ways to Reconcile
If you prefer not to build or operate reconciliation yourself, you can delegate it to a specialized reconciler already integrated with Getnet: the split information is delivered to the reconciler, which handles the closing and makes it available to your teams. Activation is arranged with Getnet as part of the commercial process.
Whichever path you choose, the starting point is the bank level: compare the credit received with the sum of the settled amounts by settlement date, and only drill down to the transaction level and the match against sales when there is a difference. Record the identifier of each schedule and each settlement so you don't duplicate movements when reprocessing a period.
Next Steps
- Statement (V3/V4): see the parameters, filters, and each block of the Statement API response.
- Settlement: see when and how each seller receives the released amounts.
On this page