Finance and accounting
Blocks
Process processing of minor costs with an emphasis on eligibility control, project assignment and auditable payment. The module digitizes the journey from uploading the note to closing by accounting, so that costs are not lost in e-mails and papers.
Context
The Bločky module is part of an internal company portal that we designed, developed and deployed for a client from the finance and accounting field. The portal consolidates dozens of corporate agendas into one environment with unified login, roles and auditable history — and the Blocks module is a key part of it.
Challenge
The small expense agenda worked outside the system — notes were sent by e-mail, on paper or via chat. Accounting manually determined to which project and person the expenditure belonged, approval was often dealt with retroactively, and there was no clear reason for rejection. There was no consistent bond to the vehicle with the PHM blocks. The result: slow closings, unclear accountability and a weak audit trail.
How we delivered
We set up the module as a fully process flow of small expenses. The employee uploads the pad, fills in the mandatory fields (project, person, type of expenditure) and the system automatically moves it to the Awaiting approval status. The approver decides to approve/reject, in case of rejection with a comment. The accounting department then closes the item as paid. Vehicle attachment is available for PHM expenses. All steps are recorded in the workflow history, including attachments and notes.
Client benefits
The small expense agenda is managed procedurally
from document upload to payment without chaos in e-mails.
Each block is linked to a project and a responsible person, so the project economy is accurate.
Approvals have a transparent history, including rejection comments and document attachments.
Accounting closes the expense as paid in one flow, without manual tracking of documents.
PHM blocks can be tied to vehicles, thus connecting the cargo with the real operation of the fleet.
Step-by-step workflow
The employee uploads a notepad (photo/scan) and fills out a form with the project, type of expenditure and responsible person
The document gets the status Awaiting approval and the system creates an approval task
The approver approves or rejects the document (if rejected with a comment)
After checking, the accountant or cashier marks the approved document as paid
The document is included in internal reports and statistics by project, person and type of cargo
Module capabilities
- uploading blocks and attachments
- mandatory ties to the project and person
- workflow approval/rejection
- comments on status changes
- designation of payment by accounting
- reporting by project, person and type of expenditure
- audit history including legacy statuses
Integrations
- projects and contracts (mandatory link)
- employees and responsible persons
- vehicles (PHM blocks)
- internal reports and statistics
Process statuses
- Created
- Awaiting approval
- Approved
- Rejected
- Paid off
Operations and further development
We designed the module with future development in mind — the modular architecture allows adding new fields, reports or integrations without interfering with the existing core. Clean code, documentation, and separate configuration files ensure that the system can be developed by another team — without depending on one person who knows "how it works."
For this type of solution, datatek, spol. s r. o. also provides long-term operational support, monitoring and SLA — so the client is sure that the system works even after years.
Module functions in detail
- Receipt upload with a photo
- An employee adds a receipt with a type (fuel, project, postage, stamps, other), date, net amount, VAT and currency. At least one attachment, a photo or scan of the document, is required.
- Data extraction from the photo
- The supplier, company ID, date and amounts per VAT rate are filled in automatically from the photo. The user only checks the data.
- Link to a project and vehicle
- Every receipt has a project and a responsible person. For fuel the vehicle is added by licence plate together with litres, so costs flow into the logbook.
- Approval
- A receipt moves through the states created, approved, rejected and paid. Rejection requires a comment; payment is marked by accounting according to permissions.
- List and export
- Filters by status, type, employee and project, export of selected receipts to a file for accounting.
- History and comments
- The detail shows a timeline of states, comments and attachments, so it is always traceable who approved the receipt and when it was reimbursed.
FAQ
Yes. A receipt cannot be saved without a photo or scan of the document, so accounting always has the original.
A regular employee sees only their own receipts. Approvers and module administrators see all of them according to permissions.
Through export to the accounting program as cash or internal documents depending on who paid. A dry run precedes the real export.
Do you need a similar module?
We will design and develop an internal application according to your processes — from analysis to deployment and long-term support.