Developers and partners
This section is for partners, integrators and technical administrators who connect invoiceR to other systems. The pages are technical and assume knowledge of REST, JSON and configuring web applications.
Overview
Section titled “Overview”| Topic | What it covers |
|---|---|
| API | The Public API and the Management API, the Swagger documentation and the format of error messages. |
| API authentication | How an external application logs in: access token with user name and password, or personal access token (PAT). |
| OpenID providers | Logging in through one or more OpenID Connect providers, for example Microsoft Entra ID. |
| Master data | Which master data invoiceR knows and how an import recognizes existing records (MappingKeys). |
| Master data import | Configuring import jobs, delivering CSV files and writing the mapping script. |
| ERP plugins | The connection to accounting and ERP systems: master data import, posting export and error feedback. |
| Hangfire jobs | Monitoring recurring background jobs and starting them manually. |
How invoiceR works with other systems
Section titled “How invoiceR works with other systems”invoiceR processes supplier invoices: documents come in, are assigned to accounts, approved and checked. It does not make payments itself. For that it is connected to the ERP or accounting system:
- Master data comes from the ERP. invoiceR regularly imports accounts, cost centers, projects, suppliers, VAT codes and other data so that users can enter valid account assignments.
- Documents arrive through several channels. Besides scanning, e-mail and upload in the user interface, an external application can also deliver documents through the API.
- Approved documents go to the ERP. After the final check, an ERP plugin passes the posting to the ERP, which makes the payment.
Recurring tasks (import, export, clean-up) run in the background as Hangfire jobs.