About

About us

An accountant who codes — fifteen years of Excel, VBA and document work, backed by an MBA in Accounting.

emdadul.com

An accountant who codes.

Most data people can extract text but can't tell whether the books balance. Most accountants can balance the books but won't write a macro. I do both.

I'm Emdadul Hoque — MBA in Accounting from the University of Chittagong, with more than fifteen years in Excel, VBA and document automation. I've processed invoices, statements, forms and reports for businesses in Bangladesh and abroad.

✓MBA, Accounting — University of Chittagong
✓Excel VBA & macros — custom tools, not templates
✓OCR & document extraction — scans, PDFs, images
✓NDA on request — files deleted 30 days after delivery

What I actually do

01

Documents in

Scans, PDFs, photographed receipts and exports become structured rows — with the source file name kept on every line.

02

Books that tie out

Duplicates, gaps and unmatched items are flagged before anyone pays. The totals reconcile to the source, not to a guess.

03

Work that repeats itself

If you do it every month, it gets a macro. One click, the same rules, the same checks — no one has to remember.

The short version of the story

I did not come to this work through a coding school. I came to it through the numbers. After my MBA in Accounting at the University of Chittagong, the job was always the same at its core: take a pile of records, make them accurate, and make them make sense to somebody who had to sign off on them.

Excel was where I learned what "good" looks like. A workbook that everybody trusts is not a workbook with clever formulas — it is one where the totals tie back to the source every single time, where nothing was typed twice by hand, and where the next person can open it and follow the trail. That is a discipline you learn from doing the work, not from a certificate.

Then the documents got harder. Scans instead of clean exports. Photographs of receipts instead of files. Forms that arrived as images because the sender did not have the data in any other form. So I learned to extract text from those too, and to build the checks that catch what extraction gets wrong — because it always gets something wrong, and pretending otherwise is how bad numbers reach a report.

The macros came last, and they came out of frustration. Same job, every month, every quarter. If work repeats, it should be a button, not a memory. That is most of what I build now: small, understandable tools that do the boring part correctly and leave the judgement to a human.

How I work with clients

01

Sample before you commit

Ten pages of your actual documents, processed first. You judge the quality before any money changes hands.

02

One person, start to finish

You talk to the person doing the work. No account manager, no handover, no "let me check with the team".

03

Fixed price, agreed first

You see the price and the delivery date before work starts. If the files turn out harder than they looked, I say so before the price moves.

A few honest limits

I do not give accounting, tax or investment advice. I prepare accurate, reconciled data — your accountant or your software does the deciding.

I am not a large agency, and I will not pretend to be one. If a job needs twenty people next week, I will say so and point you somewhere better. What I do promise is that the work is mine, it is checked, and it arrives when I said it would.

And if your documents turn out to be in worse shape than they looked, you will hear it from me before the quote changes — not after.

Send me ten pages. I'll tell you what's possible.

No obligation. A straight answer within 24 hours — and a fixed price if it is a fit.