How do I balance a POS or payment gateway settlement?
A POS or a payment gateway —Redsys, Stripe, PayPal, GoCardless— doesn’t pay in each sale separately: it groups many operations and credits the net amount in one go. That aggregated deposit is a settlement. Balancing it means checking that the sum of the operations, minus the fees, is exactly what reached the bank.
What do I need before I start?
You need a treasury account that acts as the aggregator’s bridging account, where the individual receipts are recorded before the gateway settles. The ERP finds it by its name: an account called ‘TPV Redsys (puente)’ is associated on its own with the Redsys source.
For Redsys you also need the settlement file from the portal or the bank, in CSV format. Redsys has no other way: the breakdown comes in through that file.
How does the ERP know that a deposit is the POS remittance?
By the text the bank posts it with. The daily POS credit usually includes ‘TPV’ or ‘REMESA’, the merchant number and, sometimes, the day of the sales: REMESA TPV 0123456789 12/10/2026. The ERP recognises it when you Analyse pending and treats it as a Redsys settlement for that merchant and that day, even if the description doesn’t say ‘Redsys’.
If your bank writes it another way and the ERP doesn’t recognise it, ask whoever administers the ERP to add your bank’s text to the reconciliation settings.
What if the receipts come from my online store?
Then you don’t need any file. With the store’s receipts, the ERP has already prepared the remittance it expects for each day, with all its orders inside (see Store receipts).
When you Analyse pending, the bank credit is matched with that remittance: the one with the same merchant number and the closest credit date. The bank usually credits the sales minus the POS fee, so the ERP accepts a credit below what was sold as long as the difference doesn’t exceed the POS maximum fee (3 % to begin with).
After that it does everything on its own:
- It matches each operation with its order’s receipt in the bridging account.
- It takes as the real fee what is missing between what was sold and what was credited, and spreads it across the operations.
- If everything balances, it confirms the settlement: fees journal entry, bridging receipts reconciled and the store’s receipts in Reconciled.
If it doesn’t balance, the settlement is left Unbalanced and the warning says what is happening: more came in than was sold (an order is missing from the remittance) or the difference exceeds the maximum fee (there is a receipt too many, such as a return). If two remittances from the same merchant match equally well, the ERP doesn’t choose: the line stays pending for you to link it.
How do I do it?
- Go to Treasury and click Bank reconciliation.
- In the queue, select the statement line for the aggregated deposit. Below, the Settlement block opens with its source and its reference.
- Bring in the breakdown. With Stripe, PayPal or GoCardless, click Break down (API). With Redsys, click Import CSV and choose the file.
- Check the balancing line: Gross, − Fees, = Calc. net, Announced and Difference, plus the count of Matched, Unmatched and Returned.
- Resolve by hand the lines that were left unmatched (further down).
- Click Confirm… and then Confirm.
What is balancing and when does it come out right?
The ERP adds up the amounts in the breakdown, subtracts the fees and compares that Calc. net with the Announced amount, which is what really came into the bank. The difference is shown in Difference.
In addition, each operation in the breakdown is matched with its receipt in the bridging account. First it looks for the operation’s identifier inside the receipt’s description; if it doesn’t find it, it tries by amount, and only accepts it if there is a single possible candidate.
The settlement is left Balanced when both things are true at once: the difference is zero and there is no operation left Unmatched. If either of the two fails, it is left Unbalanced and the ERP explains in a warning how much is missing and why.
Returns and chargebacks in the breakdown are marked separately as Returned. They aren’t matched against any receipt: they are processed with the normal returns procedure from the Receipts screen.
How do I match by hand an operation that was left unmatched?
In the breakdown table, lines with the status Unmatched have the Match… link.
Click it, type something in Search bridging receipt and click Search. Only the bridging account receipts that no other line has claimed yet appear. Click Match on the one you want.
The balance is recalculated straight away. When there are no Unmatched lines left and the difference is zero, the settlement changes to Balanced.
What happens when I confirm the settlement?
When you confirm, several things happen at once. If any of them fails, none is done.
The journal entry for the fees of the settlement is generated. The net amount moves from the bridging account to the bank account that credited it, with a treasury transfer and its journal entry: that way the bank reflects what really came in and the bridging account is left at zero. The bridging account receipts you have matched are marked as reconciled and no longer appear as standalone candidates. The settlement changes to Reconciled.
The transfer needs the bank line linked to the settlement. If you confirm it before you have the line, the ERP warns you and the net amount stays in the bridging account.
If the breakdown included returns, you will see a warning reminding you that they are still to be processed.
Can I confirm an unbalanced settlement?
Yes, but only on purpose. When you click Confirm… on an Unbalanced settlement, the ERP asks for the Imbalance reason (required) before letting you continue.
It is the way out for cases where the difference is explained and isn’t going to be resolved: a chargeback in the period, a hold by the gateway, an unexpected fee.
The reason is saved with the settlement as a record. If you reopen it, it is cleared: the reason belongs to that confirmation.
How do I undo a settlement that is already confirmed?
Click Reopen. The settlement goes back to Broken down and you can break it down or match it again.
The reversing journal entry for the fees is generated and the transfer of the net amount to the bank is voided. The bridging account receipts are left unreconciled again, except those backed by their own statement line: those stay reconciled because the bank closed them, not the settlement.
The breakdown already matched is kept. Reopening doesn’t delete the work done.
How do I know if a receipt is missing from the settlement?
Click Detect the month’s missing items. The ERP lists the bridging account receipts for the period that aren’t included in any settlement, with their date, their amount and their description.
It is the check the other way round: instead of looking at whether the settlement balances, it looks at whether any sale has been left out of all the settlements. A receipt that appears there month after month usually points to a misspelt description or a settlement that was never broken down.
If something goes wrong
| What you see | What has happened | What to do |
|---|---|---|
| ‘Source ‘Redsys’ does not provide a breakdown via API…’ | Redsys has no automatic breakdown | Use Import CSV with the settlement file |
| ‘There is no bridging account for source ‘…’’ | The aggregator’s treasury account is missing | Ask for it to be created with the aggregator’s name in it |
| ‘There are N treasury accounts whose name contains ‘…’’ | Several accounts fit the source’s name | The first one is used; rename the others so they don’t cause confusion |
| ‘Line N: the net amount in the file (…) does not equal amount − fee (…)’ | The CSV doesn’t match the template, or it is corrupt | Check the ; separator, the dd/MM/yyyy dates and the decimal point |
| ‘Line N: transaction ‘…’ appears more than once in the file.’ | The CSV contains the same operation twice | Correct the source file and import it again |
| ‘CSV template ‘…’ does not exist’ | That format isn’t provided for | There is only a template for Redsys; ask for it for other sources |
| The settlement is left Unbalanced and the difference is the amount of a return | There is a chargeback inside the aggregated payout | Process the return from Receipts and break it down again, or confirm accepting the imbalance |
| ‘Transaction … matches N bridging receipts by amount: left unmatched’ | There are several identical receipts and it can’t be guessed | Match it by hand with Match… |
| ‘A breakdown line can only be matched against a RECEIPT in the bridging account.’ | You chose a payment or a transaction from another account | Choose a receipt from the bridging account |
| ‘Settlement … is already reconciled: reopen it before …’ | It is confirmed | Click Reopen and try again |
| ‘The bank credited … and the expected remittance adds up to …: more came in than was sold.’ | An order from that day is missing from the remittance, or the credit is from another day | Wait for the store order to arrive, or check the day of the credit |
| ‘… the difference (…) exceeds the POS maximum fee (…).’ | There is a receipt too many in the remittance (a return, a cancelled order) or the bank deducted something else | Check the remittance’s orders; if the difference is explained, confirm accepting the imbalance |
| The store’s credit isn’t linked to any remittance | Two remittances from the same merchant match equally well | Link it by hand with the right settlement |
See also: Reconcile the bank transactions · Return a receipt
More about Banks
- How do I use my spreadsheets to reconcile the bank?
- How do I load the bank statement from a file?
- How do I reconcile the bank transactions?
- How do I connect my bank to the ERP?
- How do I set up my company’s access to Enable Banking?
- Connecting the bank and reconciling the statement
- How do I reconcile the bank month by month?
- How do I review my store’s POS remittances?
- How do I review the transactions that come in from the bank?