The records were gone.
The business still had to run.
For Jaydeep, a business owner in Kolkata, BUSY was central to day-to-day accounting. Purchase invoices had been entered over time, creating a record the business relied on. Then an office disaster left those accounting records unavailable.
The starting point was no longer the accounting system. It was the 400 physical or scanned invoices available to reconstruct the purchase entries. Each one represented information that needed to find its way back into BUSY.
Rebuild the purchase records quickly, while keeping the available invoices at the heart of the process.
According to the case account, rebuilding this backlog manually was estimated to take one to two months. Jaydeep needed a practical way to shorten that work and regain access to usable purchase records.
A backlog with no time to wait.
Invoices to rebuild from
Physical documents and scans had to become structured purchase records.
Required destination
The output needed to fit the business’s existing accounting workflow in BUSY.
Manual entry would mean reading, typing and formatting the details from every invoice. Alongside the time involved, that approach creates opportunities for transcription mistakes and further checking.
This case concerns reconstructing purchase records from available invoices. It does not describe repairing a damaged hard drive, restoring a BUSY database backup, or rebuilding every part of the accounts.
From invoice to BUSY.
One connected workflow.
eDocSmart served as the cloud-based invoice automation layer, with BUSY remaining the accounting destination. Document extraction and a local connector brought the two together.
Collect the invoices
Available paper invoices and scans became the source for rebuilding the lost purchase records.
Extract invoice data
eDocSmart processed the documents and converted invoice information into structured data.
Prepare for BUSY
The extracted records were prepared in the Excel/CSV format needed for purchase invoice entry.
Sync purchase entries
The locally installed Sync to BUSY connector transferred the processed records into BUSY.
A useful control for similar projects: review extracted details against source invoices and confirm imported entries in BUSY. The supplied case does not specify the checks performed.
For businesses using a similar approach, the aim is to reduce repeated typing while retaining source documents for review. Explore how invoice-to-BUSY automation works ↗
A two-day turnaround.
A shorter road back.
The supplied case reports that the 400 invoices were processed and purchase entries synced into BUSY in two days, compared with an estimated one to two months of manual work.
Case figures supplied by eDocSmart. The manual duration is an estimate, not a measured comparison. Timelines vary with invoice quality, complexity and review needs.
Less manual work. More breathing room.
Scroll to compare the two experiences. Scroll back to rewind.
Loading videos…
Repeated typing. A growing backlog.
Less re-keying. Purchase records in BUSY.
Illustrative animations · Case results are shown in the comparison above.
What changed for the business
- ✓ Available invoices became usable purchase entries.
- ✓ Repeated manual data entry was reduced.
- ✓ Purchase records were reconstructed in the existing BUSY workflow.
A way forward when
the invoices are still there.
The lesson extends beyond disaster recovery. A similar invoice-to-BUSY workflow can help teams working through a purchase-entry backlog or preparing historical invoices for a move into BUSY.
The essential starting point is the source material: readable invoices, the required purchase data and a clear import destination. Automation can accelerate reconstruction; regular backups remain essential for protecting the wider accounting system.
A few things to know.
Does eDocSmart replace BUSY?
In this workflow, eDocSmart processes invoices and prepares their data. BUSY remains the accounting software where purchase entries are created.
Is this a full accounting database recovery service?
This case describes reconstruction of purchase entries from available invoices. It does not establish recovery of balances, payments, receipts or an entire accounting database.
Will every 400-invoice project take two days?
No. Two days is the reported outcome for this case. Document readability, invoice complexity, configuration and review requirements can change the completion time.