How a POS or ERP reaches the NBR: four connection methods
Your software already creates the sale. The question is how the invoice travels from it to the NBR. There are four common paths, and the right one depends on what your system can do.
REST API: the best fit for modern systems
Your system sends each invoice as it is created, with a unique key so a retry never creates a duplicate. It can ask for the invoice to be signed at once and print the QR code on the receipt, while sending to the NBR follows a moment later.
File import: the practical choice for exports
Many ERPs and POS systems can export CSV or Excel files. An import reads the file, groups the lines into invoices, checks every one and keeps them as drafts until you approve. Column mappings can be saved for the next file.
Scheduled pull: when you cannot change the other system
The middleware fetches new invoices from your system on a schedule, remembers where it stopped and tries again with a delay when the source is unavailable.
Webhooks: when your system can push events
Your system posts events to a signed address. The signature covers the timestamp and the body, so an old or altered request is refused.
How to choose
- Can the system call an API at the moment of sale? Use the API.
- Does it only export reports? Use file import, then a scheduled pull if the export can be fetched.
- Does it emit events? Use webhooks.
- Not sure? Start with file import: it needs no change to your software.