DocuHub's Invoices Portal syncs supplier invoices from AADE myDATA and lets staff review AI-read uploads. insidethebox built the front end.

DocuHub's Invoices Portal is where Greek businesses manage the invoices their suppliers send them. insidethebox built the portal's front end, wrote its unit tests and ran QA. The backend and the AI engine that reads invoices are DocuHub's.

In Greece every invoice is reported to AADE through myDATA and identified by a MARK number. A company's incoming invoices therefore exist in several places and formats: the record at AADE, the PDF the supplier sent, sometimes a UBL file. Finance staff need them in one list they can search. They also need the invoices that arrive only as a PDF or a scan turned into structured data without retyping them.

The browser never calls DocuHub's API itself. Every request goes to the portal's server and from there to the API, so there is one place that handles sign-in, errors and translation of the API's messages.

Filters live in the URL. A filtered list can be bookmarked or sent to a colleague, and it survives a switch between Greek and English.

For invoices read by AI we kept a person in the loop. The engine proposes the data, an editor reviews it, and the API decides which fields may be changed.

Incoming documents lists every invoice synced from myDATA, filtered by supplier VAT number, series and number, MARK, date or document type. Each row offers the files that exist for it, such as the PDF, the AADE XML or the UBL, previewed in the browser and ready to copy or download. Lists export to CSV and Excel.

Document import takes a PDF or an image. DocuHub's engine extracts the data, the upload moves through a visible status, and an editor checks the parties, lines, totals and payment methods before submitting.

Company settings hold the myDATA credentials and the sync schedule: chosen days and a time, a sync on demand, or a sync starting from a specific MARK. People who work for several companies switch between them. Each user is a viewer or an editor, which decides both the menu they see and the pages the server lets them open.

The portal is live and in production. The places where a quiet mistake would cost most, such as which actions an upload offers at each status and how payment methods are read from the API, are covered by unit tests.