Custom or in-house system

Integration Context

Custom and in-house ERP systems present the broadest integration surface, as they lack standardised API contracts, requiring the MoF-approved ASP to develop a bespoke connector against the system's available data endpoints. The primary technical risk is ensuring complete PINT AE field mapping—particularly mandatory fields such as the buyer's VAT registration number, tax category codes, and line-level allowance structures—which are rarely captured in legacy invoice schemas.