Begin with the document
Confirm the customer or supplier, the document currency and the agreed amount. Review the supported exchange-rate field and the evidence used for the transaction date. Do not assume a saved currency code means that a live rate feed, revaluation or every payment route is configured.
Check receipt and bank evidence
A document amount, a payment amount and a bank movement can represent different currencies or dates. Follow the supported payment workflow and review the resulting evidence before calling a balance settled. Do not hide an exchange difference by silently changing the source amount.
Treat tax setup as a separate review
Country and tax fields need an operator’s review against the applicable requirements. A configured rate is not proof of filing acceptance or automatic compliance. Confirm the available report, the source events and any separate adviser or filing-system requirement.
Respect the group-reporting boundary
TerminalERP’s current group management reporting is same-currency aggregation without FX translation. It is not statutory consolidated reporting. Review membership, account mappings, completeness and the reporting period; do not infer a cross-currency group result from multi-currency document support.
Test before expanding into another market
Walk through the exact document, payment, reporting and integration requirements with a representative sample. Keep any unsupported step explicit. A successful local workflow is not proof that every country, currency or provider follows the same path.
Explore the relevant workflow
See the workflow and current product examples, read the help guides, or ask a specific product question.