Document workflow diagram: template and requirements

Learn how a document workflow diagram is created and how to show responsible parties, deadlines, approvals, and handover to accounting.

In a company, a document workflow diagram is a visual representation of a document's journey: it shows the processing sequence and the employees or departments involved. It should be clear where the document goes, who checks it, and how it reaches storage.

Uz klusa fona izcelts apgalvojums, ka dokumentu apritē ar darbību nosaukumiem vien nepietiek.

What is a workflow diagram?

It is a process diagram that lets you follow a document from start to finish. Each stage should have a clear task, rather than just a general name such as “processing”. A useful diagram also shows who the document must be passed on to.

Document workflow in a company: what to include in the diagram

Start with the process boundaries: who initiates it and where it ends. Identify the activities together with the people who actually perform them, not only from job descriptions. Document management should cover creation and receipt, registration, classification, control, storage, and access [kns.ikvd.gov.lv, arhivi.gov.lv].

Ekrānuzņēmums no arhivi.gov.lv
Screenshot from arhivi.gov.lv

Include documents received, created, and sent by the company, which document its activities. Accounting documents are not only invoices: they also include accounting records, inventory lists, and annual reports [arhivi.gov.lv, Accounting Law].

Workflow stages, responsible parties, and deadlines

Show receipt or creation, registration, checking and processing, execution or dispatch, filing, and storage. To ensure arrows have practical meaning, add the following to each activity:

  • The person performing it and the recipient at the next stage.
  • The specific activity and expected result.
  • The deadline and the time when the document is handed over.

Responsible parties can be placed in separate swimlanes or in a process matrix. In an accounting workflow document, performers and deadlines are required content, so activity names alone are not enough [kns.ikvd.gov.lv, Cabinet Regulation No. 877].

Internal document workflow: coordination and approval

Documents circulated within an organization may include employee applications, explanations, opinions, and reports. Do not confuse this group with the concept of an internal supporting document: in accounting, this is a transaction record prepared within the company [Accounting Law].

Specify the preparer, coordinators, final signatory or approver, and recipient. Show coordination separately from signing, and show the return route for corrections. Also include registration and task execution. A process management system can be used to implement such workflows.

In practice: for project orders, adapt approval routes to departments and authorization levels, allowing sequential or parallel approval. For requests, also include reminders and stopping the process with a notification to the requester after rejection.

Accounting document workflow diagram: from receipt to handover to accounting

Divide supporting-document flows by transaction type. The content specified in Sections 63-64 of Cabinet Regulation No. 877 covers the sequence of preparation or receipt, registration, checking and processing, performers, deadlines, number of copies, storage location, and retention period [Cabinet Regulation No. 877].

Mark the handover to the specific accountant and the task assigned to them separately. Handover is not the same as posting; check the posting deadlines in Article 13 of the Accounting Law [Accounting Law].

For project orders, this route also covers submitting invoices and bank statements, processing status, communication with the accountant, and handover to the finance function for payment. An e-invoicing implementation guide can help plan invoice-flow adjustments.

Paper and electronic documents in one diagram

A practical solution is to use separate branches for paper and electronic documents. Specify where the original is stored, the electronic document's metadata, and its link to the file. When moving to electronic work, add signing or certification, access, and preservation to the route; check these requirements in the Electronic Documents Law [Electronic Documents Law].

Scanning alone is not enough to decide whether to destroy the paper original. Check the conversion requirements in Article 29 of the Accounting Law and provide for documenting the conversion and destruction [Accounting Law].

In larger document-management projects, scans and electronic files are combined in a shared repository with access rights, version history, and activity tracking.

Document workflow solutions in projects and European public procurement

In project orders, clients require not only a diagram but an operational route: upload or creation, checking, approval, signing, storage, and status monitoring. The scope may also include recording approval information in the document and distributing completed files.

In European public procurement, document management is purchased together with related functions and implementation services.

  • Approval workflows, mail and invoice processing.
  • Procurement processes, controlled publication, and compliance traceability.
  • Implementation, data migration, training, maintenance, and ongoing support.

Buyers in European public procurement include hospital, development, and educational institutions, municipalities, and public transport organizations. Needs cover construction documentation, project review, electronic files, and internal approval processes.

Document workflow diagram template and its adaptation

Look for a public example on the State Treasury page “Description of personnel records management processes”, where process descriptions, diagrams, and symbols are available. It is not a mandatory template for companies, but an example of a public-sector process [kase.gov.lv].

The basic route shown below is an adaptable example, not a procedure prescribed for all documents. Replace the activities and responsible parties with your own, add deadlines and storage, then check the sequence together with the people performing it [kns.ikvd.gov.lv, Cabinet Regulation No. 877].

Ready-made workflow templates and swimlane diagram tools provide a starting point, not proof that the resulting route already fits a particular company.

When document types need separate diagrams

Separate processes when the activities, responsible parties, or approval route differ significantly, rather than creating a separate visual for every document name. In the State Treasury examples, specialized payroll and scholarship diagrams appear alongside the general personnel records management diagram [kase.gov.lv].

How does a diagram differ from document workflow procedures?

A diagram shows the route; procedures explain the rules. Procedures describe activities and the conditions for performing them, while a visual representation helps convey the sequence. An accounting workflow document may be a description or a diagram, so a drawing is not the only possible format [arhivi.gov.lv, Cabinet Regulation No. 877].

Why does a company need an organized workflow?

Visualizing a process helps identify responsible parties, weak points, and unnecessary activities. Check whether a document is requested repeatedly, waits for unclear approval, or has a recipient at every handover stage. The benefit is not a guaranteed percentage saving, but the opportunity to address identified shortcomings in a targeted way [kns.ikvd.gov.lv].

In an disorganized flow, documents may be lost, delayed, or processed repeatedly. The retention and availability of accounting documents are also the company manager's responsibility under Article 33 of the Accounting Law [Accounting Law].

In Latvia, Google search interest in this topic fell by 23% over the past 12 months compared with the previous 12 months. The peak was in February 2023, while interest is above average in January, February, and November, so a review can be scheduled before these months without treating them as a mandatory deadline.

Interese sarūk, aktīvāk meklē gada sākumā
Relative Google search interest in Latvia by month; the highest month = 100.

Is a diagram mandatory, and where can requirements be checked?

A separate drawing is not universally mandatory. Section 63 of Cabinet Regulation No. 877 allows a description or diagram; Section 66 provides an exception for a company whose accounting is maintained by its sole owner, who is also the sole board member [Cabinet Regulation No. 877].

Part three of Article 31 of the Accounting Law provides an exemption from accounting organization documents for those maintaining single-entry accounting. Check the specific company's situation in the current version of the law on Likumi.lv [Accounting Law].

Public institutions are subject to additional document-management requirements; an institution may also be a capital company owned by a public person. In the explanations of the National Archives of Latvia, check the application of the Archives Law and Cabinet Regulation No. 282, and for electronic documents also the Electronic Documents Law [arhivi.gov.lv, Electronic Documents Law].

Who prepares and approves the diagram?

Preparation can be assigned to a records manager or document-management specialist, involving the accountant and the people who actually perform the work. Accounting organization documents are issued by the company manager, who is also responsible for ensuring compliance [Accounting Law].

How do you check the diagram and implement it in daily work?

Review the visual representation with the process participants, checking its completeness and clarity. For a practical check, follow a real document and compare its actual route with the one shown [kns.ikvd.gov.lv].

  • Check that no activities have been omitted.
  • Make sure each responsible person understands the task.
  • Test correction and rejection scenarios.
  • Ensure the document reaches its storage location.

Make the diagram available to employees and explain their tasks. Reinforce the process through training and internal procedures, continuing to monitor it and address shortcomings after implementation [kns.ikvd.gov.lv].

How long does preparation take?

The sources used do not set a fixed deadline. Before planning the work, clarify the processes covered, the people involved, the availability of existing descriptions, and the scope of the review. Include review in the preparation timeline, not just drawing.

How much does developing a diagram cost?

The sources used do not set a market price. When comparing offers, clarify whether the scope includes only visualization or also process research, procedure descriptions, and implementation. Separate diagram preparation from software automation, so you compare like with like.

When should the diagram be updated?

Review it when the process or procedures change, and after shortcomings are identified during control. Also check changes to responsible parties and the systems used. The diagram must match the actual work, so do not keep an outdated route simply because it was once approved. If the workflow is implemented in a process management system, review its settings as well.

Sources

IKVD: Processes and data
LNA: Document and archive management procedures in an institution (2024)
Likumi.lv: Accounting Law (2021)
Likumi.lv: Accounting Regulations (2021)
Likumi.lv: Electronic Documents Law (2002)
State Treasury: Description of personnel records management processes (2026)

Product and design team

UX designers and frontend engineers dedicated to crafting intuitive, high-performing interfaces that align product goals with user needs across B2B solutions.