An import that fails in Hashavshevet can be structurally valid but accounting-invalid: a customer does not exist, the date is closed, a counter account is missing, a document number already exists,...
An import that fails in Hashavshevet can be structurally valid but accounting-invalid: a customer does not exist, the date is closed, a counter account is missing, a document number already exists, or amounts do not balance. Retrying the whole file after one correction can create duplicates instead of resolving rejections.
Split the flow into accepted, rejected, and pending review. Attach a stable source ID, row number, document type, returned rejection reason, and attempt time to every row. Only rejected rows return to the queue after correction. Before a retry, reconcile record count, amounts, and document numbers with the source.
Decide in advance who can amend accounting data and who can only approve an exception. A good automation does not alter a date, account, or VAT value just to make an import pass. It stops with a clear message and enables controlled handling.
Source
Keep reading
Related service
Business Automation
I build custom automations that remove repetitive work end to end.
About the author
Yehonatan Saadia
Freelance automation, web & MVP developer
I'm Yehonatan Saadia, a senior developer who builds business automation, custom websites, and MVPs for small and mid-sized companies across the US, Europe, and Israel. These guides come from real client work, not theory.
Work with meHave a project like this?
Tell me what you're trying to automate or build and I'll tell you the fastest reliable way to ship it.