Skip to content

WHAT AXIS COVERS

Add-on modules

Each module adds work Axis can do. Install the ones your business uses. Each module stands on its own, beside the thirteen core areas, and installs or comes out separately.

How they attach

%% One node per module, all of them above the foundation subgraph, each %% labelled with the title of its section on this page. scripts/check_doc_diagrams.py %% reads them that way and fails if a module is added, removed or renamed %% without this diagram following. flowchart LR Ops["Operations"] Logistics["Logistics"] Maintenance["Maintenance"] Treasury["Treasury"] Planning["Planning"] Compliance["Compliance"] RegionPk["Pakistan region"] Growth["Growth"] Integrations["Integrations"] Approvals["Approval rules"] Documents["Documents"] Esign["E-signature"] Alerts["Alerts"] Selfservice["Self-service"] subgraph Found["The foundation"] direction TB Selling["Selling"] Buying["Buying"] Inventory["Inventory"] Payments["Payments"] Tax["Tax"] Hr["HR"] Gl["General ledger"] end Any["Any record in the system"] Ops -->|"perpetual inventory from the floor"| Inventory Ops -->|"depreciation, disposal, impairment"| Gl Ops -->|"an invoice from unbilled timesheets"| Selling Logistics -->|"a supplier bill for the carrier"| Buying Logistics -->|"how the delivery travelled"| Selling Growth -->|"a won opportunity becomes a quotation"| Selling RegionPk -->|"statutory rates, withholding, returns"| Tax Integrations -->|"bank statements in"| Payments Planning -->|"variance against the actuals"| Gl Treasury -->|"a second record of the same cash"| Gl Selfservice -->|"a person's own leave and claims"| Hr Maintenance -.->|"optional link to an asset record"| Ops Esign -.->|"signs what the register holds"| Documents Approvals --> Any Documents --> Any Alerts --> Any Compliance --> Any

Two modules post to the ledger. Operations posts depreciation, disposals and stock from the shop floor. Logistics raises a supplier invoice for a carrier, which posts like any other. The rest read the ledger or keep records of their own.

Installing a module

Installing a module is a decision, so it waits for approval. Axis checks every file of the module against the list it ships with before it installs.

The example settings install Operations and Growth when the server starts. The other twelve install on request.

A module's work reaches a person through their role. In the shipped roles:

  • Operations work is held by the COO, the Manager Stores and the Manager Procurement.
  • Pakistan region work is held by the CFO and the GM Finance, with payroll settings for the Manager Admin HR.
  • The CEO role holds the work of every module.

You use most modules through the assistant. Operations also has its own screens in the menu.

See Add a module for the task.

Operations

axis-ops, version 2.2.0. 148 actions across six areas: manufacturing, advanced manufacturing, projects, fixed assets, quality and support.

What it adds: Bills of Materials, Work Orders and Inspections in the menu, with routings, workstations and non-conformances. It adds projects with timesheets, a fixed asset register with depreciation, and support issues.

Who uses it: Operations Stores Procurement

What it posts: stock from the shop floor, and depreciation, disposal, impairment and revaluation of assets. Unbilled timesheets become a sales invoice, which Selling posts.

Maintenance

axis-maintenance, version 1.0.0. 38 actions covering an equipment register, preventive and corrective maintenance, spare parts and downtime.

What it adds: a register of the machines you own, nested from a line down to its stations. It keeps meter readings, maintenance plans, maintenance work orders, the spare parts each job uses, and downtime. A machine can link to its asset record in Operations.

Who uses it: suits the Operations seat. In the shipped roles, the CEO role holds it.

Tasks: Plan maintenance

Logistics

axis-logistics, version 1.0.0. 33 actions covering shipments, carriers, routes, freight charges and carrier invoicing.

What it adds: how a delivery travelled. It keeps shipments with their tracking events and proof of delivery, carriers and their rates, multi-drop routes, and freight charges spread across the goods they carried. Two reports compare carriers on performance and on cost.

Who uses it: suits the Sales and Stores seats. In the shipped roles, the CEO role holds it.

What it posts: a verified carrier invoice becomes a supplier invoice in Buying, and posts like any other.

Treasury

axis-treasury, version 1.0.0. 34 actions covering bank accounts, cash positions, cash forecasting, investments and inter-company transfers.

What it adds: how much cash there is, where it sits, and whether there will be enough. It keeps bank balances by date, cash forecasts run 30, 60 or 90 days ahead, a liquidity report, investments, and transfers between group companies.

Who uses it: suits the Finance seat. In the shipped roles, the CEO role holds it.

What it posts: Treasury keeps its own record of cash, beside the ledger's bank accounts. Bringing the two together is a step you take on purpose.

Planning

axis-planning, version 1.0.0. 30 actions covering budget versions, scenarios, forecasts and variance analysis.

What it adds: several budget versions, scenarios you can copy and edit, forecasts, and variance broken out line by line. A scenario can be approved, locked and archived, so last year's plan stays readable.

Who uses it: suits the Finance seat. In the shipped roles, the CEO role holds it.

What it posts: Planning reads the ledger's actual figures to work out each variance.

Compliance

axis-compliance, version 1.0.0. 37 actions across four areas: internal audit, risk register, control testing and policy management.

What it adds: the evidence that someone checked. It keeps audit plans and their findings, a risk register with a history of scores and a risk matrix, control tests and their results, and policies.

Who uses it: suits the Finance seat and your auditors. In the shipped roles, the CEO role holds it.

Pakistan region

axis-region-pk, version 1.0.0. 14 actions covering FBR federal sales tax, provincial sales tax on services, income tax withholding in both directions, NTN and STRN registration, monthly sales tax returns and FBR digital invoicing payloads.

What it adds: NTN and STRN registrations for the company, its customers and its suppliers. It states the federal and provincial sales tax rates, and works out withholding tax on both sides. It prepares the monthly sales tax return and the data for an FBR digital invoice. A company bound to the region also works out salary tax by the Pakistan rules.

Who uses it: Finance Administrators

The GM Finance prepares the monthly return, and the CFO files it. Filing waits for approval, and locks that month's figures as declared.

Growth

axis-growth, version 2.10.0. 164 actions across four areas: CRM, advanced CRM, analytics and the AI engine. It is the largest module in the repository by action count.

What it adds: the work before a quotation. It keeps leads and where they came from, opportunities moving through your own pipeline stages, contacts and the companies they work for, and campaigns. A won opportunity becomes a quotation in Selling. Analytics reads the ledger for ratios and trends.

Who uses it: suits the Sales seat. In the shipped roles, the CEO role holds it.

What is in the sales pipeline, and what is it worth?

Integrations

axis-integrations, version 2.2.0. 90 actions covering connectors, sync scheduling, field mapping, bank statement import and a set of platform-specific connectors.

What it adds: links to the other systems you use. It keeps connectors with their credentials stored apart, scheduled syncs with a record of each row that failed, field mappings, and bank statement import.

Who uses it: suits the Administrators and Finance seats. In the shipped roles, the CEO role holds it.

Approval rules

axis-approvals, version 1.0.0. 12 actions covering multi-level approval routing, delegation and the audit trail behind it.

What it adds: sign-off on a document by other people, in order. A rule names the document and the condition, such as a purchase order over a set value. Its steps name who approves at each level. Approvers can delegate, and every decision is recorded.

This is a different job from the approval gate. The gate asks the person who made a request, at the moment it runs. Approval rules route a document to other people, over days if need be.

Who uses it: every seat that signs off on documents. In the shipped roles, the CEO role holds it.

Documents

axis-documents, version 1.1.0. 31 actions covering a document register with versions, tags and links, plus templates and PDF printing.

What it adds: a register for your files, with each revision kept beside the one before. Tags classify them, and links tie a file to any record, such as a signed delivery note to its delivery. It keeps a retention period and a legal hold, and prints documents to PDF from templates.

Who uses it: every seat that keeps files. In the shipped roles, the CEO role holds it.

E-signature

axis-esign, version 1.0.0. 12 actions covering signature requests, the signing ceremony and the audit trail behind it.

What it adds: signature requests on a document, with their signatories and reminders. A request ends signed, declined, cancelled by the sender, or voided after completion. Every event on a request is recorded, which is what a signature is worth in a dispute.

Who uses it: every seat that sends documents for signature. In the shipped roles, the CEO role holds it.

Alerts

axis-alerts, version 1.0.0. 20 actions covering alert rules, notification channels, and the email substrate the rest of the product sends through.

What it adds: alert rules, such as stock below a level or an invoice past its due date, and the channels they reach: email, webhook, Telegram or SMS. You acknowledge each alert once it is dealt with, so the list works as a queue. It also holds the email accounts and templates that the rest of Axis sends through.

Who uses it: every seat that wants to be told. In the shipped roles, the CEO role holds it.

Self-service

axis-selfservice, version 1.0.0. 24 actions covering permission profiles, portal configuration, sessions and activity logging.

What it adds: a narrow view of their own records for people outside your staff. An employee sees their own leave and claims, and a customer sees their own invoices. Each profile is scoped to its holder's own records, and every session and action is logged.

Who uses it: set up by the Administrators seat. In the shipped roles, the CEO role holds it.

Next