Where do reconciliation files come from?
From the provider, retrieved through credentials held in the contract. When a provider requires them, the contract carries a dedicated reconciliation section with the file server host, username and password, the merchant identifier used by that provider for reporting, and the folder path where the files are published. Those values usually sit in the provider back office under settlement or reporting access.
In detail
From the provider. The platform retrieves them using credentials held in the provider contract, so reconciliation runs on the same data the provider uses for settlement.
The reconciliation section of a contract
When a provider requires it, the contract carries a dedicated reconciliation section with:
- The file server host.
- The username and password.
- The merchant identifier that provider uses for reporting.
- The folder path where the files are published.
Those values usually sit in the provider back office, under settlement or reporting access. Your merchants or your team enter them once in the contract, alongside the payment credentials, and the platform collects the files from then on.
Why it sits in the contract
Keeping reconciliation access next to the payment configuration means each provider relationship is described in one place. When a contract is reviewed, suspended or replaced, its reporting access follows. It also keeps credentials under the same governance and audit trail as the rest of the contract.
Once collected, provider data is mapped into one model and reconciled against your merchants' records. Every provider, brand and channel then reads from a single reconciled view, which is what makes consolidated reporting possible across a multi-provider setup.