← All services
What survives a decade

System Integration & Compliance

System integration, electronic invoicing and fiscal reporting, cloud and third-party APIs.

Speaking the protocol is the easy half. The time goes into what the remote system does when things are not going well: a submission accepted now and rejected an hour later, an error delivered inside a 200 response, a timeout that does not mean the request failed, a rate limit nobody documented. None of that is in the specification, and it is what decides whether the integration still works a year from now.

I connect systems over REST / Web API, WCF / SOAP, message queues, GIS (ArcGIS) and cloud services (AWS S3 / SES / Cognito, Azure SQL).

For Romanian fiscal compliance I implement e-Factura and SAF-T end to end, tested against the tax authority's real endpoints and not only against the specification. e-Factura is the example of everything above: the upload returns an index, not a verdict. The invoice is settled minutes or hours later, so the work is in polling for the state, reading the rejection reasons, and resubmitting - not in the call that uploads it.

More work

Rejoining the server...

Rejoin failed... trying again in seconds.

Failed to rejoin.
Please retry or reload the page.

The session has been paused by the server.

Failed to resume the session.
Please retry or reload the page.

An unhandled error has occurred. Reload 🗙