ERP integration development and troubleshooting

Use this review when orders, invoices or other records are missing, duplicated or repeatedly failing between applications.

• Share the systems, interface design if available, sanitized transaction examples, error records and expected outcome.
• I trace the agreed transaction path and examine ownership, validation, retries, duplicate handling and reconciliation.
• The deliverable is a failure map, documented risks and prioritized recommendations with checks for recovery and acceptance.

Connector development and production corrections are separately scoped. Discuss an integration review.

These anonymized examples describe my personal engineering work.

Email PDFs to Business Central sales orders

I developed a workflow using Azure Document Intelligence to process PDF email attachments and create actual sales orders in Business Central. Different PDF layouts and item numbers that did not exactly match were key engineering challenges. The implemented workflow connects document processing with ERP order creation.

Legacy system data to Dynamics GP through OneDrive

I developed a .NET utility running on a legacy system outside the ERP network and on a different domain. It uploads data to OneDrive at scheduled intervals for integration with Dynamics GP orders and updates involving items, pricing and quantities. The utility provides periodic data transfer across that network boundary.

For a new connection, I define system ownership, field meaning, validation and the point at which a transaction is complete. For an existing failure, I trace the actual data path and identify where records are missing, duplicated, rejected or altered.

I build exception handling, logging and retry behavior around the risks of the transaction. A retry should not create a second invoice or leave an order partially processed.

Reconciliation checks connect technical execution with business outcomes. Support instructions explain how to investigate an exception and when a person needs to intervene.

The work can produce an interface specification, data mappings, a connector or repaired integration, exception reports and a support runbook. Validation covers the expected transaction as well as rejected records, duplicate submissions and interrupted processing.