Financial Revolution: setup and help

Upload the module ZIP in Modules > Module Manager and install it. Open Sell > Finances > Settings > Configuration.

Select the intended shop. Review your document numbering before creating documents. Give employees the view, add and edit permissions they need for the finance pages. Changing records, exporting data and downloading documents use the relevant controller permissions.

Open Settings > System Check if the module reports missing tables or installation problems. Keep a database backup before configuring numbering or importing financial data.

For multistore reporting, select the intended shop before comparing figures. Sales and expense report queries use the current shop. Customer VAT validation history follows the customer account rather than a separate shop field, so do not assume separate validation histories for shops sharing the same customer.

The Configuration screen groups fields under Invoices, Corrections, Proformas, VAT, Costs and PDF.

The default category mapping is:

{
  "operating":"Operating Costs",
  "marketing":"Marketing",
  "shipping":"Shipping & Logistics",
  "personnel":"Personnel",
  "software":"Software & Services",
  "other":"Other"
}

The basic numbering placeholders are {PREFIX}, {YYYY}, {MM} and {####}. For example, INV/2026/06/0001 is the shape produced by the default pattern for the first applicable number in June 2026.

Open Settings > Numbering. Configure the sequence for each Document Type. Set Prefix, optional Suffix, Format, Current Number, Reset Mode, Min Digits and Active.

Current Number is the last number used. The next document increments it. Use the current sequence state when continuing an existing series. The module reserves sequence numbers using database locking.

The Numbering form supports {PREFIX}, {SUFFIX}, {YYYY}, {YY}, {MM}, {DD}, {####}, {###} and {##}. New/default sequence behavior follows the configured prefixes, format and reset mode. Review the actual row before generating documents.

Open Settings > Document Templates. Set the translated Name, Type, Header HTML, Footer HTML, Custom CSS, optional Logo, Primary Color and Active. Content fields start empty unless supplied by a default template. Preview the result, then download a sample PDF to check page size, logo, text and totals.

Invoices

Open Documents > Invoices. The list reads PrestaShop's native order_invoice records with their orders, customers, totals and order states. Use View Order to inspect the source order and the PDF action to retrieve its invoice. Existing native invoices are not replaced by a separate module invoice database.

Corrections and refunds

Open Refunds to inspect records from the shared refunds package. Open Documents > Corrections to inspect correction records and use View or Download PDF. Credit-slip hooks connect refund activity to module corrections. Check the credit slip, correction reference and amounts together.

Proformas

Open Documents > Proformas and create a proforma. Fill Customer Email, Items (JSON), Valid Until and optional Notes. The items must be a valid JSON array accepted by the model. Totals are calculated from the items, and a proforma number is assigned from its sequence.

Use View or Download PDF to check the saved document. Convert to Invoice creates and stores the module's invoice conversion snapshot and document number. It can attach to an existing order invoice when the proforma is linked to an order. Do not assume a standalone conversion creates a new paid PrestaShop order.

Rejected or expired proformas cannot be converted. A proforma whose validity date has passed is also rejected by conversion. Already converted records retain their conversion state.

Sales reporting reads native PrestaShop invoices and orders. On order validation, the module ensures document numbering for invoices already attached to that order and writes audit information. The order-status hook records an audit event; it does not create a separate revenue ledger or enter your expenses. Add actual costs through Costs & Expenses.

Open Costs & Expenses > Partners. Set Company Name, then any Contact Name, Email, Phone, VAT Number, Website, address fields, Country and Notes you need. Use Active to control availability.

Open Costs & Expenses > Categories. Fill translated Name and optional Description. Set Color for charts and reports. New active records can be selected when recording expenses.

Open Costs & Expenses > Expenses and create an expense:

1. Enter a required Title and optional Reference and Description.
2. Select the Partner and Category where applicable.
3. Enter Amount (tax excl.) and Tax Rate. Check Amount (tax incl.) after calculation.
4. Record Refunded Amount or Discount Amount when applicable. Numeric amounts start at zero.
5. Set the required Expense Date, optional Due Date, Payment Status and Payment Date. Payment status can be Pending, Paid or Partial; new cost records start pending.
6. Use Product / Category Allocation if the expense belongs to selected catalog entities.
7. Add an Attachment if needed, then save and check the record.

The attachment field accepts supported receipt or invoice documents and images. The PHP process needs write access to the module's financial upload directories. Hosting limits and server-side file validation still apply.

Open Costs & Expenses > Recurring Costs. Fill Title, optional Description, Partner, Category, the amount and tax fields, Frequency, Start Date, optional End Date and Next Generation.

A new recurring record defaults to monthly, Auto Approve off and Active on. If Next Generation is empty, the model uses Start Date. Leave End Date empty for an indefinite schedule.

Use the page's generation action for one record or the action to generate due costs. Generating costs creates expense records and advances the next date. Auto Approve transfers approval to generated costs. Due expenses are generated through these actions, rather than automatically by a scheduled task.

Open Tax & VAT > VAT Validation. Review the customer, VAT number, country, status, source and validation date. Use the customer search and validation actions to create or update a record, or Revalidate to request a new result.

The validator checks country-specific format and can use VIES through PHP SOAP. If VIES is unavailable, a format-valid result is recorded as a format check. It is not the same as authoritative VIES confirmation. If remote validation fails, check PHP SOAP, outbound connectivity and the displayed result source.

Open Tax & VAT > VAT Reports for date-based VAT reporting. Compare the selected period with the underlying sales and expense records before using exported figures.

The Dashboard displays revenue, costs, profit, margin, VAT balance, VAT collected, VAT paid, outstanding invoices, recent invoices and overdue costs. Cost figures depend on records in mprfinancial_cost. Use the same period when comparing charts and lists.

Open Reports > Profit & Loss or Reports > Cash Flow, choose the period and inspect the report.

Open Reports > Export. Choose the data type, date range and format. You can export invoices, corrections, costs, VAT reports, profit and loss, cash flow, customer VAT and the audit log. Available formats are CSV, XLSX, JSON and XML. XLSX requires PHP ZipArchive.

The export refuses an empty data set. Files are written under upload/mprfinancial/exports/, so the PHP process needs permission to create and write that directory. Download the generated file and check its record count and totals.

The audit_log export contains order-edit history. It does not include the separate financial audit log.

Start with one known invoice and one test expense. Confirm their list entries, totals, dates and dashboard period. Download a PDF and export the same period to CSV. If you use XLSX, open the generated workbook as a separate check.

For a proforma, check the items, calculated totals, number and PDF before conversion. Test numbering on a copy of your shop if you are migrating an existing series.

If a page or form reports missing structures, run System Check and inspect the error logs. If your installed package is missing required files, replace it with a complete release.

If an action is denied, check the employee profile's permissions for that page. If totals look wrong, check shop scope, date range, cost entry completeness and the source invoice or credit slip. The reports use the data available in the shop; they are not a substitute for maintaining complete accounting records.

Back up financial tables and uploaded files first. Uninstall removes the admin menu and module configuration. It does not drop the module's own financial tables by default. The shared refunds package has separate cleanup that depends on whether other modules use it.

Requires PrestaShop 1.6.1 or later and PHP 7.1 or later.