Every module, answered.

Cargonio is freight-forwarding software with the accounting built in. Air and sea, export and import, courier consignments, quotations, invoicing, a double-entry ledger, HR and payroll, and 150 reports all live in one workspace, so operations and the books are the same set of records rather than two systems tied together at month end.

Freight forwarders and consolidators who run their own jobs, raise their own invoices and keep their own books — and the accountant who has to close the month afterwards. The screens, menu order and document numbering follow the way a forwarding office already works rather than a generic ERP.

There are 9 modules. A workspace is switched on for the ones it needs and sees nothing of the rest.

• Freight Forwarding — jobs, documents, billing, master data, management
• Finance — chart of accounts, vouchers, banking, opening balances
• Reports — 150 report screens across the operational, finance and payroll menus
• Courier — consignment booking and consignment accounts
• Sales — customers, foreign agents, sale and tele call books, app quotations
• HR Management — employees, attendance, leave, payroll and offboarding
• My Portal — the employee self-service portal
• Inventory — an item file
• Logs — the workspace activity log

No. Entitlements are granted per workspace, and not just per module — every screen inside a module is granted separately, and so is every right on that screen. A forwarder who keeps books elsewhere can run operations only; a workspace with no staff records never sees the HR menu.

Freight Forwarding alone carries 8 job and shipment entry screens and 30 money-document screens, on top of 86 code and master-data screens shared across the modules. Finance adds six voucher types. Reports adds 150.

Nothing on your staff machines. It is a web application: everyone signs in with a browser, and there is no client to roll out, no per-desk licence file and no version drift between the front office and accounts.

There is no separate app to install. The system is used through a browser.

Master data first, then the books, then people, then live work.

• Initial Setup — parties, associates, airlines, shipping lines, destinations, currencies, charge codes and the rest of the code files
• Finance → Initial Setup — group codes, control codes, the chart of accounts, analysis codes, then opening balances
• Branches and the fiscal year, so numbering and the year filter are right from the first document
• Users, user categories and roles
• Then import history, or start keying live jobs

Yes. Opening Balances under Finance → Initial Setup is there for exactly that: you bring in balances as at your changeover date and start posting from there, rather than re-keying the year that has already been audited.

PKR. Documents can be raised in any currency you set up, but every ledger posting is converted to PKR first, so the trial balance never adds dollars to rupees.

Yes. Branches are set up under Freight Forwarding → Management → Settings, each with its own details, and job and voucher numbering is keyed on the branch so two stations never collide on a number.

The software imposes none. What a user can reach is decided by their abilities, not by a seat count.

The master data the rest of the system picks from: parties, associate (foreign agent) codes, sub-agents, delivery agents, stock owners, airlines and their charges, shipping lines and transporters, vessels and voyages, sectors, countries, destinations, currencies, commodities, container types, networks, chargeable codes (MOP), invoice charge codes, signatories, other payable types, job types, job statuses, terms and conditions, SPO codes, K.B. incentive rates and stock-owner finance codes.

A party is the local counterparty you bill or buy from — shipper, consignee, customer or vendor. The party file carries the trading details (addresses, NTN, sales tax number and type, CNIC, contacts, import/export registration) plus a credit limit and the B/L Hold, D/O Hold and Release Order flags.

A party is local; an associate is a foreign agent. It matters for billing: local invoices and other charges are raised against a party, while invoices and credit notes to and from foreign agents are raised against an associate, and the two sit in different report menus and different control accounts.

SPO is the salesperson the business is booked under. Each SPO carries a share percentage, a split share, a finance code and the parties associated with them — which is what the whole SPO-wise report menu (outstanding, aging, gross profit by lane, sales register, party list) is built on.

The Currency Codes screen holds them, and it holds four: an invoice rate, an AWB rate, an open-market rate and an inter-bank rate. They are maintained by you, not fetched from a feed, so the rate a document is booked at is a rate you chose and can defend.

Yes. The AirLine Codes and Charges screen holds the airline itself, and AirLine Charges (Per Airport) holds the per-airport charge schedule beside it, so one carrier can carry a different rate card at each station.

They are the method-of-payment codes a job is rated under. They are selected on the job so the rating and the invoice agree on how the shipment is being charged.

Invoice Charges Codes is the catalogue every charge line picks from, so the same charge is spelled the same way on every invoice and the charge-wise reports actually add up.

Yes — Job Types and Job Status are both code files you maintain. The status you define is what the shipment-status boards push onto jobs.

The Terms and Conditions code file. Documents print the terms you keep there rather than text retyped into each one.

Signatory Codes holds them, and a voucher carries a signatory code and a designation for the printed copy.

It holds the incentive rates behind the three K.B. reports for air export — detail of incentives, the incentive summary and K.B. payable to parties.

The owner of the airway-bill stock you fly on. Stock Owners holds them, and Stock Owner Finance Codes holds the finance codes each one maps to, which is how owner-wise sales summaries are grouped.

No — the code files take a CSV import, so an existing party, airline or destination list can be brought across as a file. See the data-migration section.

Air Waybill Stock (received from airline) and an Available AWB Stock enquiry, the MAWB job screen, the HAWB job screen, local invoices, other charges payable, and invoices and credit notes both to and from foreign agents.

Stock received from an airline is entered on the Air Waybill Stock screen — as a range or one waybill at a time — and the Available AWB Stock screen queries what is left. Three reports cover it: available stock, stock used, and an airline-wise summary.

Because they are separate documents with separate numbering and separate rights. The MAWB screen is the master/consol; the HAWB screen is the house shipment. Both write into the same job file, so a consol master and its houses stay linked.

Yes. The dimensions grid computes volume weight as length × width × height × pieces divided by the divisor for the dimension type — 6000 for Air Cm, 366 for Air In, 166 for Air Lb, 4000 for By Land Cm and 5000 for Courier Cm — and the chargeable weight is the greater of gross and total volume weight.

Yes — the air-export rating carries a CW / GW / PC selector, so a charge is applied on charge weight, gross weight or per piece.

Yes. A master that consolidates house bills prints a Manifest listing them all on one landscape sheet, alongside the Air Waybill and House Air Waybill forms.

The invoice you raise on a local party for the shipment — the Local Invoices Entry and Printing (Air-Export) screen. It is the document that carries sales tax and that posts revenue and receivable to the ledger when it is finalised.

Other Charges Payable (Air-Export). It is a payable, so it posts to cost and to the agent/vendor payable control, and a payment voucher can later be allocated against it.

Four screens per lane: invoices to foreign agents, credit notes to foreign agents, invoices and debit notes received from foreign agents, and credit notes received from foreign agents. Outbound ones are receivable, inbound ones are payable, and the reports treat them accordingly.

The Air-Export report menu carries 18 reports, including pending invoices, party-wise invoice detail and summary, invoice-wise sales register, daily booking (consol), airline and sector-wise booking, destination, commodity and carrier summaries, fortnightly airline sales/WHT, job-wise and party-wise gross profit, the job sheet, job-wise finance expenses, other charges payable detail and the shipment register.

Jobs entry and document printing, other charges payables, refunds from shipping lines, local invoices, the loading programme, and invoices and credit notes to and from foreign agents.

On a container grid on the job, with the container details and a detention amount per row. Container types themselves are a code file under Initial Setup.

It groups the shipments going onto one sailing. It is its own screen with its own numbering, and it prints as a landscape Loading Program document.

Yes. A consol job carries its house bills on a houses grid, prints an MBL and an HBL per house, and can print a manifest across them. There is a dedicated Detail of Consol Jobs report.

The Refund from Shipping Lines screen. It is raised against the shipping line rather than a party, and the reports treat a refund as something that reduces cost, not as revenue.

Yes — the sea invoice carries a container rate model as well as a flat charge grid, so a rate quoted per box does not have to be pre-multiplied by hand.

Yes. The sea export job carries Form E references and dates among its header fields, alongside the loading programme number, shipper invoice details and the HBL format code.

The Sea-Export report menu carries 22 reports — the largest of the lanes — including pending invoices, party-wise invoice detail and summary, invoice-wise sales register, detail of jobs by job, shipping-line agent, SPO, foreign agent and party, consol job detail, carrier and destination summaries, other charges payable detail, refunds received, job-wise and party-wise gross profit, the job sheet, finance expenses, daily booking, commodity summary and the shipment register.

Manifest inbond shipments, inbond shipments entry and document printing, local invoices, other charges payable, and invoices and credit notes to and from foreign agents.

It is the arrival capture: the master and the houses on it are keyed from the incoming manifest, in the units the manifest uses (pieces, cartons, bales, pallets, packages or skids). The inbond shipment screen is then where each shipment is worked and billed.

On the houses grid of the master, each row carrying its own house number, pieces, weights and chargeable weight — and each one printable as a house document in its own right.

Yes. Delivery Order is one of the job print templates and is offered on all four lanes, along with the job sheet.

The party file carries B/L Hold, D/O Hold and Release Order flags, and a credit limit, so the commercial position is recorded against the party rather than remembered by one person.

Sixteen reports, including the inbound shipments register, an origin-wise inbond register, pending invoices, party-wise invoice detail and summary, invoice-wise detail, job-wise and party-wise gross profit, the job sheet, job-wise finance expenses, other charges payable detail, daily booking, destination, commodity and airline summaries, and the shipment register.

Manifest inbond shipments, inbond shipment entry and document printing, other charges payables, refunds from shipping lines, local invoices, and invoices and credit notes to and from foreign agents.

Yes — port of loading, port of discharge, port of shipment, via port, wharf, terminal and shed are all header fields on the job.

Yes, with its own screen and its own numbering series, and its own shipping-line-agent-wise refund report.

Seventeen reports, including the inbound and origin-wise registers, invoices not required, party-wise invoice detail and summary, invoice-wise detail, job-wise and party-wise gross profit, the job sheet, finance expenses, other charges payable detail, refunds received, daily booking, destination, commodity and shipping-line summaries, and the shipment register.

Deliberately, yes. Each lane has the same shape — jobs, local invoices, other charges payable, agent invoices and credit notes — so staff who learn one lane can work another, and a report written for one lane has a twin in the others.

Automatically, from a counter keyed on the lane, the branch and the year — so each station has its own run and the year restarts it. Leaving the job number blank takes the next one; you can also type one.

Yes, on the Auto J.V / system configuration screen. Branch-wise numbering, department-wise job and invoice sequences, a yearly restart for jobs and for invoices, and separate runs for local and international invoices are all switches.

Open, Final or Cancelled — the state of the folder itself. Separately, the job carries a shipment status from your own Job Status code file, with a status date and remarks, and that is what the shipment-status boards move.

Draft, Checked, Final, Cancelled or Paid. Draft is a working document; Checked is an optional review step before it is committed; Final commits it and posts it to the ledger; Cancelled is a voided document, which keeps its number; Paid is reached when receipts or payments have settled it in full.

It is stamped with who finalised it and when, and a balanced journal voucher is posted to the ledger — every leg in PKR, converted at the document's own rate. If the voucher would not balance to the paisa, the save is refused rather than posted.

A finalised document is voided, not deleted. Voiding keeps the number and the charge lines, records a reason, and reverses the ledger posting; un-voiding puts it back at the status it held and re-posts it. The series never has a hole in it, which is what an auditor is looking for.

The job carries a documents grid for recording what has been received and when. For storing files, the Data Bank under Management holds uploaded documents tagged by module and category.

A place to record security deposits or guarantees against the job with their dates, so they are not tracked in a side spreadsheet.

Yes. Picking the job on the document fills in its master and house numbers, and that link is what job-wise gross profit, the job sheet and job-wise finance expenses are computed from.

Yes. A document is entered in its own currency with its own exchange rate, and the PKR equivalent is what is posted, summed and reported — so a USD invoice and a PKR invoice can sit in the same report without the total being meaningless.

Local invoices carry a tax type (PST, SST, PRA, SRB, ST or VAT), a rate and a sales-tax invoice number, and a second provincial tax (PRA/SRB) can be charged alongside the federal one with its own rate and number. They post to separate liability accounts. Credit notes, agent documents, payables, refunds and quotations carry no tax.

On the receivable side there is an advance income tax (WHT recoverable) control account that a document's withholding posts to, and there is a fortnightly airline-wise sales/WHT summary for air export. Withholding on the payable side is captured on the document but is not yet posted to a liability account — that wiring is a disclosed piece of work in progress.

The party file holds a credit limit and there is a configuration switch for checking it. It ships off, so nothing is blocked until you deliberately turn it on.

Finalised receivable invoices — local invoices and invoices to foreign agents — less what receipt vouchers have been allocated against them. A payable, or a credit note, is not a receivable and does not appear there.

Yes. Quotations are a screen of their own under Transactions Menu (Others), and a quotation can be converted rather than retyped. There is a List of Quotations report.

No. A quotation has no financial effect, so finalising one posts nothing; the same is true of a document receipt.

The record of documents received — who handed what over and when — printable, and covered by the Document Receipt Register report.

Other Invoice Entry and Printing, and Other Charges Payable Entry and Printing, both under Transactions Menu (Others). They carry no lane, and there are dedicated reports for them — party-wise detail, an invoice-wise sales register, service invoice gross profit and an all-modes payable detail.

A read-only inbox of quotation requests, so enquiries arriving from outside land somewhere the sales desk can see them rather than in one person's mailbox.

The transaction screens raise the freight invoices tied to a job. The Billing section holds a separate tax-invoice register used for fiscalised invoicing, with its own numbering and its own PST report.

Yes. Billing invoices can be posted to the Punjab Revenue Authority e-IMS fiscalisation service with the payload the PRAL POS component manual specifies, either one at a time or as a sync of everything pending, and the fiscal invoice number that comes back is stored against the invoice.

Your PRA settings on the workspace — the POS ID issued to you by the portal, and a default PCT code. Without them there is nothing to authenticate the submission with.

No. A void invoice, or one with no line items, is refused before it is submitted, and an invoice that has already synced is not sent twice.

The provincial sales tax register for the Billing invoices, exportable as a file for filing.

Not today. The freight transaction invoices post themselves to the ledger on finalising; the Billing module's own tax invoices do not yet, and that wiring is disclosed work in progress rather than a hidden gap.

Users, Settings, User Category, User Roles, Auto J.V Finance Codes Setup, Data Block Date and Data Bank.

It is where operations meets the chart of accounts: which finance codes the automatic postings use, plus the numbering and validation switches (branch-wise sequences, yearly restarts, AWB validation against stock, credit-limit checking, automatic house numbers, whether a job may be opened without a quotation reference).

The branch file — each branch with its own details — which is what the branch switcher, branch-wise numbering and the branch filter on reports read from.

The period lock. Any date on or before it is a closed period: a document or voucher dated inside it cannot be edited or un-finalised, and the automatic poster refuses to post into it too — it tells you to re-date the document or move the block date.

Not yet. Editing and un-finalising inside a closed period are refused, but voiding currently gets past the lock. It is a known gap being closed; until it is, restrict the Void right to the people who should be closing periods anyway.

A document store inside the workspace. Files are uploaded and tagged by module and category, with the uploader and size recorded, so scanned paperwork lives with the system rather than on somebody's desktop.

The grouping a user belongs to — Supervisor, Data Entry, Only View and any you add. Roles are defined against those categories.

It defines a named role as a set of rights per screen, and applying it to a user syncs their permissions. It is a template: editing a role does not silently change what somebody already signed in can do until it is applied again.

A Total Records view of what is in the system, plus four shipment-status boards — air export, sea export, air import and sea import.

They are worklists. You tick the shipments that have moved and push a status onto them in one go, rather than opening each job. Because that is an edit, it needs the edit right on the board, not just view.

The boards are for the day — what is where right now. The report menus are for the period — registers, gross profit, outstanding and aging.

Two entry screens — C/N Booking and C/N Accounts — plus two consignment reports in the Reports module: Detail of C/Ns, and Detail of C/Ns with shipper and consignee.

They are the same consignment record seen from two desks. Booking is where the consignment is keyed; Accounts is where it is completed and priced — and finalising on the Accounts side is what posts it to the ledger, using the C/N income and expense codes from the Auto J.V setup.

Un-Final, Final or Void. The list also filters by Posted and Un-Posted, which are derived from whether a ledger voucher exists rather than stored as a status.

Yes. Each consignment carries a dated, timed status trail — local customs clearance, departure, arrival at and departure from the airline hub, arrival at destination, customs clearance at the foreign hub, handover to the carrier, and arrival and departure at the port of loading and destination.

By mode of payment — Account, Cash, COD or FOC — with the consignment typed as DOX, NON-DOX or FLYER and as courier or cargo. Sales tax can be applied as P.S.T, S.S.T or S.T.

The consignment note, an invoice, a pro-forma invoice, a sales-tax invoice, a weight sheet and labels — on letterhead or plain paper, in PKR or foreign currency, with a copy for the shipper or the courier.

Yes — the voucher's job-linkage block carries a COR-CN job type and a courier C/N number, so an expense can be booked against the consignment it belongs to.

Customers, foreign agents, cargo types and reason types as master files; the Sale Calls and Tele Calls books; and the App Quotations inbox.

They are two books of the same kind of record — a visit and a phone call — kept separately so the reporting can tell them apart. Each is a separate screen with its own rights.

Yes — Detail of Calls by call date and Detail of Calls by follow-up date, so a rep can be given their follow-ups for the week rather than reading through the book.

They are the coded outcomes a call is recorded against, so "why we did not get it" is a field that reports rather than free text nobody reads.

Yes, in the Sales report section — a Thai Airways / any airline sale report and its foreign-currency twin — on top of the five airline sales reports in the air-export menu.

Real double entry. Every posting is a balanced voucher of debit and credit legs, and a voucher whose debits and credits differ by as much as half a paisa is refused and rolled back rather than saved.

Three levels — Group Codes, then Control Codes, then the Chart of Accounts itself — with Analysis Group Codes and Analysis Codes as a second dimension for cost/profit analysis, and an Opening Balances screen for the changeover.

Six: BPV - Bank Payment Voucher, BRV - Bank Receipt Voucher, CPV - Cash Payment Voucher, CRV - Cash Receipt Voucher, JVR - Journal Voucher, LVR - Loan Voucher.

Draft → Checked → Final, with Un-Check and Un-Final to step back, and Void / Un-Void for a mistake. Each of the six actions is a separate right, so the person who enters a voucher need not be the person who checks it or the person who finalises it.

Per company, voucher type, year and branch, four digits padded. Voiding keeps the number, so the series has no holes.

Yes — cheque number, date, clearing date, status (un-cleared, cleared, returned, cancelled or bounced) and instrument type. There are thirteen instrument types, from an open or payee-only cheque through bank transfer, online transfer, credit card, PO, TT, cash, personal cheque, online personal, digital wallet, ATM transfer and RTGS.

A receipt voucher (BRV or CRV) is allocated against the party's outstanding finalised invoices. Each allocation records the PKR value it settles; the total is what outstanding and aging subtract, and a document settled in full is marked Paid.

Yes, mirrored. A payment voucher (BPV or CPV) is allocated against outstanding payables — other charges, and invoices and credit notes received from foreign agents. A payment voucher cannot settle a sales invoice, and a receipt cannot settle a payable.

The difference between the PKR booked and the PKR realised is posted on the settlement voucher as a realised exchange gain or loss, as a self-balancing pair against the control account — so the control clears at exactly its booked value and the voucher still balances.

Yes, one thing, and it is disclosed rather than hidden: re-saving a receipt voucher can drop the settlement allocations it carried. Until that is fixed, check the allocations after editing a receipt that has already been applied to invoices.

Post Dated Cheques, Cheque Book and Bank Reconciliation, plus the cash and bank books and cheque reports in the finance report menu.

They are the lighter day-to-day cash screens — deposits and expenses against categories you define, with a transactions view over them — for workspaces that want them alongside the formal voucher entry.

Trial balance, balance sheet, profit and loss, and profit and loss with comparative figures, plus the accounts ledger, account balances, cash/bank book, list of vouchers, list of final vouchers, cheque reports, post-dated cheque detail, job-wise voucher detail and an analysis-code detail of accounts.

They tag a voucher line with a second dimension — a cost centre, department or activity — so the same expense account can be reported several ways without inventing a new account for each.

Yes. A document links to its job, so job-wise gross profit reports exist for every lane, the job sheet carries a profit block, and job-wise finance expenses shows what has been booked against it from the vouchers.

150 report screens, grouped into the menus the office already navigates by: parties, airline sales, K.B., AWB stock, SPO-wise, one menu per trade lane, other transactions, courier, sales, MIS, finance and payroll.

Every report is the same shell with the filter widgets it needs — dates, branch, year, party, agent, SPO, airline, shipping line, currency, mode, job type, account and so on — so once you have learned one report's filter bar you have learned them all.

Yes. Every report can be run on screen, printed, or downloaded as a CSV that Excel opens directly, with the UTF-8 marker so party names come through correctly.

Yes, where the workspace has its SMTP details configured — and emailing is a separate right from viewing, because sending figures out of the building is a different act from reading them.

A report renders up to 5,000 rows in one run and tells you when the rest was truncated, so a mis-set date range cannot take the workspace down. Narrow the filters, or export in slices.

Yes. Any figure summed across documents is converted to PKR first, at the document's own rate — otherwise a dollar invoice would be added to a rupee one and the total would mean nothing.

Revenue is local invoices and invoices to foreign agents, less credit notes we issue. Cost is other charges payable and invoices received from foreign agents, less credit notes received and shipping-line refunds. The difference is the gross profit, and it can be cut by job, party, SPO or lane.

Yes, party-wise and SPO-wise, alongside outstanding detail, a paid/unpaid detail report and statements of account.

Yes — a sale tax register and a party-wise sale tax register in the Parties menu, plus the PST report in Billing.

Yes. Each of the 150 reports is its own entitlement with its own view right, so a salesperson can be given their SPO reports without being given the trial balance.

Balance sheet, profit and loss, profit and loss with comparative figures, and a daily activity report.

Seven: list of monthly deductions, employees' monthly leaves detail, the monthly payroll register in both regular and summary form, the salary slip, a bank letter and a list of employees.

The employee file and its supporting codes (designations, departments, shifts, shift roster, locations), assets issued to staff, leave, attendance, payroll, appreciations and awards, offboarding, holidays, news, policies, surveys and custom data fields.

Code and number, name, designation, department, contact details, joining and probation dates, notice period, location, shift, who they report to, whether they manage, annual CTC and monthly salary, and their status — active, resigned or terminated.

From the Employees screen. You can create a portal login when adding them, or give, change and remove access afterwards from the employee's access page. There is also a "view as" so an administrator can see exactly what the employee sees.

Three ways: the Mark Attendance screen for the day, the attendance records list, and employees clocking in and out from their own portal. There is an attendance summary and an attendance-correction screen for fixing a wrong day.

Leave types are defined by you; employees apply from their portal; HR sees the requests on the Leave Requests screen and approves or rejects them. The portal shows the employee their remaining, paid and unpaid leave.

You run the month as a draft, check it, then finalise. A final run locks the month — it cannot be re-processed — and applies that month's loan instalments to the loan balances.

Gross is basic plus increments, the master allowances (house rent, fuel, conveyance, medical and other), the month's arrears and bonus, overtime at the hourly or daily rate, and leave allowance. Deductions are the month's entered deductions, tax, EOBI, provident fund and medical contribution, late time, loan instalments due, and without-pay leave days falling in the month. Net is the difference, and every component is stored on the line so a slip prints from stored figures.

The daily rate is basic plus increments divided by the days in the month; the hourly rate divides that by the employee's duty hours, which default to eight.

Yes. The Loan Master File holds the loan; instalments marked for deduction and in effect are taken by the payroll run, capped at the remaining balance, and applied to the balance when the month is finalised.

The Monthly Allowance & Deductions screen, keyed per employee per month — arrears, bonus, overtime, late time, tax and deductions — with Monthly Leaves alongside it.

Not yet. A final payroll run locks the month and produces the registers and slips, but it does not create ledger entries — payroll-to-ledger wiring is disclosed work in progress, so today the salary journal is passed by voucher.

The salary slip is one of the payroll reports and prints from the browser; it is not yet produced as a PDF file to attach. Employees can see their own payroll in their portal.

Resignations, warnings, complaints, letter heads and generated letters — so the paperwork of an exit is on file rather than in an inbox.

Yes. Custom field groups and custom fields let you add what your business needs, and employees can maintain their own custom data from the portal where you allow it.

Whoever holds the edit right on the screen that owns the record. Leave, corrections, resignations, complaints and expense claims each approve under their own screen's permission, not one blanket "approver" role.

The employee self-service area. Staff sign in and see only their own dashboard: their attendance, leave, payroll, assets, appreciations, company news, policies, holidays, surveys and profile.

Only staff with an employee record. The workspace administrator does not — they run the company rather than filing their own leave — so the menu never offers them a dead end.

Clock in and out, apply for leave, file an attendance correction, submit an expense claim, file a resignation or a complaint, answer a survey and maintain their own custom data fields.

Yes — payroll, pre-payments and increments/promotions are all in the portal's Payroll section, for that employee only.

No. The portal is scoped to the signed-in employee's own records, and every portal screen is a separate entitlement so a workspace can switch off anything it does not want staff to see at all.

Yes. Creating a portal login is a choice made per employee; the HR module works whether or not anybody outside the office has an account.

It holds an item file — the goods or stock items a workspace needs to name and price. It is deliberately small: this is not a warehouse management system, and it does not claim to be one.

No. AWB stock has its own register under Air Export, with its own reports. Inventory is a general item file.

Yes. The Activity Log records changes with the user who made them, the record they touched and the time. Where an administrator was acting as somebody else, the real person behind the action is recorded too.

Whoever you grant the Activity Log screen to. It is its own module entitlement, so it can be given to a director or an auditor without giving them anything else.

Yes — documents and vouchers carry who checked them and when, who finalised them and when, and a voided one carries the reason and the status it held before.

Yes. Imports are logged, so a batch of records that arrived by file can be traced back to the file and the person who loaded it.

By CSV. 130 screens carry an import flow of their own — upload the file, map its headers onto the screen's fields, run a dry pass that validates every row, then commit the valid rows in one transaction.

No, and it would be wrong to say so. 130 screens do — the code files, the transaction lists, the job and document screens and the voucher screens. Screens that are enquiries, dashboards or reports have nothing to import into.

You find out before anything is written. The dry run validates every row against the same rules the form uses and reports the failures by row; you fix the file and run it again. Nothing is half-imported.

Screens with a natural key — a code or SKU — match on it and let you choose to skip duplicates or update them. Screens with no natural key insert every row, so re-running such a file would double it.

Up to 5,000 data rows per file. A bigger history is split and loaded in batches.

Probably not. UTF-8 with or without a byte-order mark, UTF-16 exports and legacy Windows-1252 files are all read correctly. Anything else is rejected with a clear message rather than imported as gibberish you would have to find later.

No. Rows are written through exactly the same path the forms use, so tenant scoping, model events and the screen's own validation all apply. Imported jobs, documents and vouchers land as drafts and never post themselves to the ledger.

Cells are defused against CSV formula injection at the point of parsing, so a spreadsheet exported later cannot execute something that arrived in an import.

Yes. Every list screen exports the current list — same filters, same tab, same working context — as a CSV, and the export carries the full importable field set rather than just the visible columns, so a download re-imports as-is.

It is a usable copy of a screen's data, and it is the right tool for moving data between systems. It is not a substitute for the database backups taken on the server.

Codes before the records that reference them. Parties, agents, airlines, shipping lines, destinations, currencies and charge codes first; then the chart of accounts and opening balances; then jobs; then documents. An import that references a code you have not loaded will fail the dry run rather than create a half-linked record.

Very. Access is granted per screen and per right, which comes to 1,268 distinct permissions across the product. Someone can be allowed to enter a voucher but not check it, print an invoice but not void it, or run one report but not another.

View, Add, Edit, Delete, Print, Final, Un-Final, Void, Un-Void, Un-Lock, Check, Un-Check, Email, Approved, Opening Balance and Use — not a generic create/read/update/delete four. Transaction screens carry the workflow rights; a code file carries the plain ones.

An entitlement is what your workspace has bought or been given; a permission is what a particular user holds within it. Both must say yes. That is why a screen can be switched off for the whole company without editing every user.

No. Define a role once as a set of rights per screen and apply it to users. Because a role is a template, editing it does not silently change what an existing user can do until it is applied again.

A clear message telling them the section or action is not enabled and to contact their administrator — not a dead 404 that looks like a bug.

Yes, and it is the reason check and final are separate rights from create. Give data entry the create right, a supervisor the check right, and the finance manager the final right, and no single person can push a voucher through on their own.

Only through impersonation, which is logged — the activity trail records both the account acted as and the real person behind it — and a scoped support account can only reach the modules it was granted, even by typing the URL.

Yes. Impersonation can be read-only, so a session opened to diagnose something cannot change your records while it is open.

Yes — Google sign-in sits alongside the usual email and password, once it has been configured for the workspace.

The fiscal year and branch you are currently working in, chosen from the switcher at the top of the app. Operational lists narrow to it, and report filters default from it, so you do not re-set the year on every screen.

From the switcher. It is a view preference rather than a change to data, and it will not accept a branch or year belonging to another workspace.

Yes by default — job and voucher counters are keyed on the branch — and it is a switch, so a business that wants one run across every station can fold them together.

They are configured for your workspace as part of setting it up. There is no self-service fiscal-year creation screen yet — ask support and it is done for you.

Set the Data Block Date. Everything dated on or before it is frozen: finalised documents and vouchers inside it cannot be edited or un-finalised, and the automatic poster refuses to post into it, telling you to re-date the document or move the boundary.

Yes — move the block date back. It is a deliberate act by whoever holds that screen's rights, and it is recorded.

One thing today: voiding a document is not currently stopped by the lock. It is a known gap under repair. Until then, keep the Void right narrow.

From a job: the airway bill, house airway bill, bill of lading, house bill of lading, job sheet, delivery order, loading programme and manifest. From a money document: the invoice, credit note, debit note and receipt. Vouchers print as a voucher, debit note, credit note, receipt or cheque.

Job and money documents render as PDFs, in portrait or landscape as the form requires, and can be emailed. Some listings and the salary slip print from the browser rather than as a PDF file.

Yes. Vouchers and consignment documents carry a stationery choice — pre-printed letterhead, or plain paper with the header drawn — plus options for the stamp, payee-only marking and the "computer generated document" footer.

Yes — vouchers and consignment documents carry a PKR / foreign-currency print toggle.

Yes, where one has been uploaded for the workspace. Very large image files are skipped rather than embedded into every page.

Yes, where the workspace has its own SMTP details configured, and emailing is its own right. If mail is not configured the system says so plainly rather than silently failing to send.

Your SMTP host, port, username and password on the workspace. Mail then goes out from your own address, which is what a customer expects to see.

In your own workspace on the hosted system. Every record carries the workspace it belongs to and every query is scoped to it, so one client's data is never reachable from another's session.

The software is shared; the data is not. Scoping is applied at the data-access layer rather than remembered screen by screen, and it is covered by automated tests.

Backups are part of the hosted arrangement, and on top of them the database is dumped immediately before every deployment and that dump kept on the server for a fortnight — so a bad update is recoverable without reaching for last night's copy. A deployment never drops or re-seeds production data.

Deliberately conservatively, because the system holds your books: a database dump first, then the update, with the app briefly in maintenance mode for the migration and brought back up even if a step fails.

Only for the short migration window, and updates are scheduled rather than sprung on you.

It is a standard PHP and MySQL application, so it can. Talk to us about it — the hosted arrangement is the default because updates and backups are then ours to worry about.

Yes. Every list screen exports to CSV and every report exports to CSV, so you can take a copy whenever you want without asking anybody.

Yes. Ask us and we will walk you through a workspace with real-shaped data in it — your own trade lanes, your own documents — rather than a slide deck.

No. A demo workspace is seeded with representative sample data so the screens, reports and totals look like a working office. Nothing in it belongs to a real client.

See the pricing page. Because modules are entitled separately, what you pay follows what you switch on.

Less than you would expect, because the menu order, screen labels and document numbering follow the way a forwarding office already works. The heaviest lift is usually the accounts side, and that is where we spend the setup time.

Cargonio is built by CodeSummix.

Contact us and we will look at it with you. Where it helps, a support session can be opened read-only, so we can see the screen you are on without being able to change anything.

Tell us. This page lists the handful of known gaps by name rather than hiding them, and that is how we would rather run it.

Being straight about them: voiding a document is not yet stopped by the period lock; re-saving a receipt voucher can drop its settlement allocations; withholding tax on payables is not yet posted to a liability; payroll and the Billing module's own tax invoices do not yet post to the ledger; fiscal years are created for you rather than on a screen; and salary slips print from the browser rather than as PDF files. Each is being worked on.