Integration engine

Your ERP or billing system has its own names for invoice fields. Each country has its own rules for what an invoice must contain. The Integration engine sits between the two.

You build an integration: a mapping from your fields to GETS, the Complyance standard invoice format, plus the extra fields a country requires. Once an integration is tested and linked to a source, invoices from that source are converted with it. You do not write conversion code for each country.

Where to find it

Open the Developer portal from the portal switcher at the bottom of the sidebar. Integration engine is the first item in the menu.

The page lists your integrations. If you have none yet, you see Please create your first Integration. Choose New Integration to start.

How an integration is built

Setup is a guided flow that opens with a short overview screen. The bar at the top shows where you are: Configuration, API Keys, Payload, Mapping, Testbed.

1. Select a Country. The country you need to be compliant in. You can add more countries to the same integration later.
2. Select Transaction Type. The kind of document this integration handles.
3. Manage API Keys. Create the key your system uses to send data. The secret is shown once. Copy it before you close the window.
4. Payload Selection. Choose a payload your system has already sent, or choose Upload JSON or Excel to add a sample file.
5. Mapping Preview. Review the fields Complyance found in your payload.
6. GETS Field Mapping. Match your fields to the standard format. See Map your fields to GETS.
7. Country Field Mapping. Add the fields that only this country asks for. See Map country fields.
8. Testbed. Run your payload through the mapping and read the validation results. See Test your mapping.

If you go back and change the country or the transaction type, the steps after it start again. The portal warns you before this happens.

What mapping looks like

Mapping is a table. One column lists the GETS fields, grouped into sections such as header, seller, delivery, payment and totals. Beside each field you pick the matching field from your payload, and a format if the value needs one.

Each field carries a label:

• Mandatory: the invoice cannot be sent without it.
• Conditional Mandatory: needed only in some cases.
• Mapped or Not mapped: whether you have dealt with it yet.

Use the Unmapped Mandatory filter to see what still blocks you.

After it is built

Each integration in the list shows how complete its mapping is, how many test cases have passed, which countries it covers, and whether it is Active, Inactive or In Progress.

From the list you can edit the GETS or country mapping, add a country, rename or delete the integration, and choose Manage sources to decide which source systems use it. You can also import a mapping, or transfer one from another workspace. See Manage integrations.

An integration marked Managed by partner was set up for you by your partner. You can view it, but only your partner can change it.