EazLink guide
What does a custom ERP need before a CamInvoice API integration?
A custom ERP CamInvoice API checklist for invoice data, idempotency, response storage, error handling and project-specific GDDE access.
Short answer
A custom ERP needs a stable invoice event, a document identifier that survives retries, complete buyer and seller data, and a place to store the platform response. The team must then obtain the current GDDE onboarding and interface material for its approved role. An API endpoint found online is not enough to establish production access. The official SOP describes test data, invalid submissions, security and final validation.
Official context: GDDE, Ministry of Economy and Finance
What to remember
- Define a stable source ID before writing the first adapter.
- Separate data rejection from transport failure.
- Keep test evidence and the approved interface version with the project.
Make the source contract boring
Emit one invoice event with a stable ID, legal entity, buyer, lines, tax and totals. If a network request times out, reuse the same source ID so support can determine whether the document was accepted or still needs action.
Do not build a permanent mapping around an unverified sample payload. The customer's membership and interface version determine the final fields.
Test the failure path early
The GDDE SOP explicitly includes invalid-data submissions and error handling. Add a sample with missing buyer data, another with a corrected amount and an interrupted call. Record the request, response and person who resolved each case.
A useful pilot ends with the answer visible in the ERP. If an invoice is pending, the system must not quietly mark it as accepted.
Questions before implementation
- What is the stable invoice ID across retries?
- Which response means accepted, rejected or still pending?
- Who approves the current interface and test environment?
Quick questions
Is public CamInvoice API documentation enough to go live?
No. Production permissions, approved role, interface version and test evidence need to be confirmed for the project.
Can an integration retry every error automatically?
No. Data rejection usually needs correction, while a temporary transport problem may need a controlled retry. The actual response rules depend on the approved interface.
Read next
Sources: GDDE, Ministry of Economy and Finance ยท GDDE, Ministry of Economy and Finance. Used for factual background only.
Have a custom ERP API already?
Share a sanitized invoice payload and the response you need back. We can review the contract before anyone builds to an assumed endpoint.