Connect your current ERP to the Fawtara journey.

Start with the invoice source

List the systems creating invoices and corrections. Include legal entities, languages, currencies and tax treatments. Check whether APIs, exports or integration events can expose the required structured data.

Map the lifecycle

Agree how source records become validated documents, how they reach the appointed provider, and how accepted/rejected statuses return to users. Test credit notes, retries, duplicate prevention and an unavailable downstream service.

Agree the boundary

Keep accounting ownership and data correction clear. Confirm provider onboarding and the supported production scope separately. Do not assume a named ERP has a ready connector before an installation-specific compatibility review.

Prepare a discovery pack

Bring a redacted invoice, correction example, API documentation, monthly volume, legal-entity count and the OTA applicability evidence your team is using.