Development for the public sector

Government audit software for federal transfers and state spending

Two complementary systems: one to record and validate public spending, and one to manage each audit and its files, from the initial request to the final report.

  • Supreme audit institutions
  • State governments
  • Spending agencies

Benefits for the audit institution

Organized information before the audit and complete evidence at the end.

Spending information in one record

Revenue, expenditure and transfers are classified by funding source and expenditure chapter, with the same structure for every state and spending agency.

Verifiable tax receipts

The CFDI invoices that support spending are validated in bulk before the review, so auditors start from verified receipts.

Audit traceability

Every action stays in the audit file: who performed it, when it was approved and which document supports it, from the request to the final report.

Technology control stays with the institution

The solution runs on your servers and is delivered with source code, so the institution decides how it is operated, safeguarded and evolved.

Key features of both systems

Each system can run on its own. Together, spending information feeds audit planning and execution.

System 1

Recording and validation of federal transfers and state spending

A web platform where state governments and spending agencies report how funds were used, and the audit institution follows up on the information received.

  • Entry of revenue, expenditure and transfers by funding source and expenditure chapter.
  • Bulk validation of the CFDI invoices linked to each record.
  • Upload alerts for missing, late or inconsistent information.
  • Risk reports to guide audit planning.
  • Reports by state and by spending agency.
  • Web access for state governments and spending agencies with per-user permissions.

System 2

Audit process management

An internal tool to plan, carry out and document each audit, with the audit file at the center of the team’s work.

  • Management of audit teams, assignments, permissions and approvals.
  • Work program and timeline for each audit.
  • Official letters, records, working papers and reports generated from templates.
  • Integration with Document Control Systems (SCD).
  • Government audit files from the initial request to the final report.

Government audit files, from the request to the final report

Sample structure of an audit file. Stages, templates and approvals are configured to each institution’s regulations.

  1. Request

    Information request letter and acknowledgment of receipt.

  2. Planning

    Work program, assigned team and audit calendar.

  3. Execution

    Documents received, validated CFDI invoices and working papers.

  4. Proceedings

    Records, official letters and approvals for each stage.

  5. Findings

    Observations with their supporting evidence.

  6. Final report

    Report issued from a template, with references to the audit file.

Request a walkthrough of a sample audit file

Why choose our government audit solution

Differentiators built around the requirements tender documents and technical annexes usually include.

Technical annex requirements covered

On-premise deployment on Ubuntu Server, Docker, Nginx and Node.js, in testing and production environments.

Source code and perpetual rights

The institution receives the source code with perpetual usage rights and does not depend on an external service to operate.

CFDI experience since 2014

Realvirtual builds electronic invoicing and CFDI certification software. Validating tax receipts is part of our daily work.

Integration with your document operations

The audit system connects to the institution’s Document Control System instead of duplicating it.

Knowledge transfer

Training for users and administrators, and complete documentation for installation, operation and code.

Development with evidence

We plan before writing code and record the review of every change, which makes technical oversight of the project easier.

Implementation process

A staged path, with reviewable deliverables at each step.

  1. Requirements review

    We compare the technical annex with the solution and document the scope of each system.

  2. Testing environment installation

    We deploy the solution on the institution’s infrastructure to validate features and SCD integration.

  3. Initial setup

    We load catalogs, funding sources, users, permissions and templates for letters, records, working papers and reports.

  4. Training and acceptance

    We train users and administrators and support acceptance testing.

  5. Production and support

    We install in production, deliver source code and documentation, and start the support period.

Frequently asked questions

Can the solution be installed on the institution’s servers?

Yes. It is installed on-premise on Ubuntu Server with Docker, Nginx and Node.js, in both the testing and the production environment.

Is the source code delivered?

Yes. Delivery includes the source code with perpetual usage rights, along with technical and operating documentation.

Who uses each system?

State governments and spending agencies use the spending system to report information. The audit team of the supreme audit institution uses the audit management system.

How does it integrate with our Document Control System?

The integration is defined during the requirements review, based on the mechanisms your SCD provides, and validated in the testing environment.

Can you take part in a public tender or restricted invitation?

Yes. We can review the tender documents and technical annex, present a demonstration and prepare the technical proposal.

Is your institution preparing a tender for audit systems?

We review the technical annex with your audit and IT teams, and prepare a demonstration of both systems.

RealvirtualES

Development for the public sector

Government audit software for federal transfers and state spending

Two complementary systems: one to record and validate public spending, and one to manage each audit and its files, from the initial request to the final report.

  • Supreme audit institutions
  • State governments
  • Spending agencies

Benefits for the audit institution

Organized information before the audit and complete evidence at the end.

Spending information in one record

Revenue, expenditure and transfers are classified by funding source and expenditure chapter, with the same structure for every state and spending agency.

Verifiable tax receipts

The CFDI invoices that support spending are validated in bulk before the review, so auditors start from verified receipts.

Audit traceability

Every action stays in the audit file: who performed it, when it was approved and which document supports it, from the request to the final report.

Technology control stays with the institution

The solution runs on your servers and is delivered with source code, so the institution decides how it is operated, safeguarded and evolved.

Key features of both systems

Each system can run on its own. Together, spending information feeds audit planning and execution.

System 1

Recording and validation of federal transfers and state spending

A web platform where state governments and spending agencies report how funds were used, and the audit institution follows up on the information received.

  • Entry of revenue, expenditure and transfers by funding source and expenditure chapter.
  • Bulk validation of the CFDI invoices linked to each record.
  • Upload alerts for missing, late or inconsistent information.
  • Risk reports to guide audit planning.
  • Reports by state and by spending agency.
  • Web access for state governments and spending agencies with per-user permissions.

System 2

Audit process management

An internal tool to plan, carry out and document each audit, with the audit file at the center of the team’s work.

  • Management of audit teams, assignments, permissions and approvals.
  • Work program and timeline for each audit.
  • Official letters, records, working papers and reports generated from templates.
  • Integration with Document Control Systems (SCD).
  • Government audit files from the initial request to the final report.

Government audit files, from the request to the final report

Sample structure of an audit file. Stages, templates and approvals are configured to each institution’s regulations.

  1. Request

    Information request letter and acknowledgment of receipt.

  2. Planning

    Work program, assigned team and audit calendar.

  3. Execution

    Documents received, validated CFDI invoices and working papers.

  4. Proceedings

    Records, official letters and approvals for each stage.

  5. Findings

    Observations with their supporting evidence.

  6. Final report

    Report issued from a template, with references to the audit file.

Request a walkthrough of a sample audit file

Why choose our government audit solution

Differentiators built around the requirements tender documents and technical annexes usually include.

Technical annex requirements covered

On-premise deployment on Ubuntu Server, Docker, Nginx and Node.js, in testing and production environments.

Source code and perpetual rights

The institution receives the source code with perpetual usage rights and does not depend on an external service to operate.

CFDI experience since 2014

Realvirtual builds electronic invoicing and CFDI certification software. Validating tax receipts is part of our daily work.

Integration with your document operations

The audit system connects to the institution’s Document Control System instead of duplicating it.

Knowledge transfer

Training for users and administrators, and complete documentation for installation, operation and code.

Development with evidence

We plan before writing code and record the review of every change, which makes technical oversight of the project easier.

Implementation process

A staged path, with reviewable deliverables at each step.

  1. Requirements review

    We compare the technical annex with the solution and document the scope of each system.

  2. Testing environment installation

    We deploy the solution on the institution’s infrastructure to validate features and SCD integration.

  3. Initial setup

    We load catalogs, funding sources, users, permissions and templates for letters, records, working papers and reports.

  4. Training and acceptance

    We train users and administrators and support acceptance testing.

  5. Production and support

    We install in production, deliver source code and documentation, and start the support period.

Frequently asked questions

Can the solution be installed on the institution’s servers?

Yes. It is installed on-premise on Ubuntu Server with Docker, Nginx and Node.js, in both the testing and the production environment.

Is the source code delivered?

Yes. Delivery includes the source code with perpetual usage rights, along with technical and operating documentation.

Who uses each system?

State governments and spending agencies use the spending system to report information. The audit team of the supreme audit institution uses the audit management system.

How does it integrate with our Document Control System?

The integration is defined during the requirements review, based on the mechanisms your SCD provides, and validated in the testing environment.

Can you take part in a public tender or restricted invitation?

Yes. We can review the tender documents and technical annex, present a demonstration and prepare the technical proposal.

Is your institution preparing a tender for audit systems?

We review the technical annex with your audit and IT teams, and prepare a demonstration of both systems.