Documentation

DigitalManager helps Pakistani businesses create and manage FBR-aligned digital invoices, keep buyer records organised, and work through PRAL integration with a clear, step-by-step workflow.

Use the sections on the left to jump to setup, day-to-day invoicing, and product areas. This page is the canonical in-app documentation hub; you can link to /docs from anywhere on the marketing site.

Start from the Log in page to access the app. Trial access lets you explore the dashboard, invoice flows, and settings before going live.

• Use a secure password and keep your session private on shared devices.
• Complete company profile and FBR-related fields so submissions stay consistent.

Connect your environment to FBR by completing the in-app FBR token setup (see app setup) and verifying company identifiers match your PRAL registration.

Rotate or refresh tokens when your integration policy requires it; invalid tokens will block submission until updated.

• Stable internet for API calls to FBR services.
• Correct NTN / registration data in company settings.
• Buyer details validated before issuing invoices.
• Review tax rates and scenario rules applicable to your business type.

The Dashboard is your signed-in home at /dashboard. It loads company-wide statistics from the app and updates automatically about every five minutes. Use the refresh control in the top-right corner whenever you want the latest numbers without waiting.

The first row of cards gives you a quick picture of volume and pipeline: Total Invoices (everything in the system), then Draft, Validated (ready for FBR submission), and Submitted (successfully sent to FBR). Trend-style hints under the cards explain what each count represents.

Below that, Submission progress shows how many invoices are submitted out of the total, as a count, percentage, and progress bar. The PKR financial summary shows the total value of submitted invoices for the current month and the average invoice value—useful for a quick read on throughput and ticket size.

When something needs attention, an Alerts panel may appear. If the FBR token is not configured, complete token setup (for example under FBR token setup) so validation and submission can run. If invoices fail submission or validation, the dashboard surfaces short error excerpts and links you to the filtered invoice list—for example failed submissions or validation failures—so you can open each invoice and fix data before retrying.

Quick actions shortcut to common tasks: open invoices, open reports, jump to items pending FBR submission when that count is non-zero, or open failed and validation-failed items in one go when applicable.

Recent activity lists the latest invoice-related events (such as draft, validated, submitted, or error states) with timestamps, so you can confirm what changed recently without leaving the dashboard.

Open /invoices after signing in. The screen has three top tabs: Create Invoice, Invoice List, and Import (spreadsheet import plus a PDF scan placeholder). The two main day-to-day workflows are the list and the composer described below.

Invoice List tab

Purpose: your control centre for invoices already saved for the company—find, review, filter, and act on them without opening the full composer unless you need to edit.

• The list loads when you open this tab and when you press Refresh. Data is scoped to your company.
• New Invoice resets the composer and switches to Create Invoice for a blank document.
• Date filter: all time, today, this week, this month, or a custom calendar range (with clear actions).
• Status filter: one or more of draft, validated, validation failed, submitted, or failed—or all.
• Search narrows the loaded set by text in fields such as FBR invoice number, date string, invoice type, buyer name, and status.
• The table shows serial number, invoice ID (FBR number when present), date, type, buyer, amount, a status badge, and per-row Actions.
• Actions depend on status: view details (and load line items); view objection for some validation-failed cases; edit (not for submitted invoices—loads the composer for others); validate for draft / failed / validation failed; submit to FBR when validated; download PDF when submitted; failed rows may offer a resubmission path from the menu.
• Empty states explain whether there is no data or filters returned nothing, and may offer Create Invoice when appropriate.

Create Invoice tab

Purpose: the full invoice composer—header data, buyer, seller snapshot, line items, FBR validation, local save, and submission—in one layout.

• Alerts at the top show validation errors, success text, and when FBR validation returns valid, a clear message that you can proceed to submit.
• Invoice information includes type, date, reference, PO and MIV numbers (MIV is debounced against the validation API when entered), and in sandbox a scenario selector for FBR test data.
• Buyer information covers registration type, NTN/CNIC, name, province, and address. Use Select buyer (searchable, paginated) or Add new buyer. Buyer province is required before HS code / UOM flows; unregistered buyers can drive further tax using the percentage from company settings.
• Seller information in the sidebar is prefilled from your logged-in company profile for consistency with FBR.
• Invoice items: one or more lines with sale type, HS code (loads UOM options from FBR), UOM, quantities, tax values, discounts, and SRO-related fields where applicable. Optional extra fields (for example FED payable) can appear based on settings. Add or remove lines; the card footer shows PKR totals (excluding tax, sales tax, further tax, grand total).
• JSON opens a modal with the payload for debugging. Save only writes the invoice to your database without FBR submission (requires at least one line). Validate invoice calls FBR validate and updates the alerts. Save & submit runs the submit flow when prerequisites are met (logged in, valid form, MIV where required, validation not invalid, and so on).
• Reference lists (invoice types, provinces, HS codes, UOMs, transaction types, etc.) come from FBR APIs; sandbox also loads scenarios. The active sandbox vs production mode follows your company's FBR environment setting.

Scenario testing helps you exercise FBR sandbox invoice posts using pre-defined payloads tied to your company, so you can confirm tokens, seller fields, and official test cases before relying only on ad-hoc invoices.

Testing Scenarios (/scenarios-testing)

After you sign in, this screen is for your company only. You can preview what would be sent for each FBR test scenario, run a sandbox submission, and see which scenarios have already succeeded.

• If your user is not linked to a company, the page tells you that scenarios are per company and to contact an administrator.
• The list is built from the scenarios you enabled under Settings → Company → FBR Given Scenarios (see Settings). If nothing is configured, the page explains where to add them.
• Each row shows the scenario name, a related sale type label if available, Tested or Pending, plus JSON and Test actions.
• JSON opens a read-only preview: the invoice date is set to today and seller details are taken from your company profile, so you see the payload as it would be sent—without memorising field names.
• Test runs the same preview through the app to FBR's sandbox post flow. You must be logged in and your company needs a valid FBR token in Settings; otherwise you will see an auth or token error.
• When FBR accepts the post and returns an invoice number, you get a success message, the row moves to Tested, and the result is stored for that scenario. If something fails, a message summarises the reason when the system has one.
• Only one test runs at a time: other Test buttons are disabled and the active row shows a spinner.
• Below the table, a simple progress bar shows how many scenarios are tested out of the total.
• This page is for sandbox testing only, not live production filing. Pending means that scenario has not yet completed a successful sandbox run.

Open /settings after signing in. This is the per-company area for FBR environment and token, tax and invoice UI options, FBR scenarios assigned to the company, and default HS codes. Data is read and written through /api/companies/… and /api/settings.

You need a company on your account; otherwise the page explains that settings are per company. The header shows which company you are managing.

A vertical nav on the left switches between Company and Products. The right side shows one card for the active section and a Save button below (behaviour depends on which tab is active).

Company tab

When this tab opens, the app loads the company record (including token, environment, and scenario ids) and the global scenarios catalogue from GET /api/scenarios for the scenario picker.

• Read-only: name, NTN/CNIC, address, contact (phone and email), province — used across invoices and FBR payloads.
• Further Tax % — number between 0 and 100 (supports decimals). Used for unregistered-buyer further-tax behaviour on invoices; validated before save.
• Environment — Sandbox or Production; drives which FBR endpoints the app uses (invoice form, HS loading, etc.).
• Token — company FBR bearer token (masked input). Required for FBR calls and for loading HS codes where applicable.
• Extra inputs in invoice — toggles for optional line fields on the invoice composer: Tax Withheld, Extra Tax, Discount, FED Payable, SRO Schedule, SRO Item. Off hides the field in the UI; payload shape is unchanged.
• FBR Given Scenarios — searchable multi-select of scenario names (with sale-type hints). Stored on the company as a comma-separated list; same set as the scenario control on invoices and for Testing Scenarios.
• Save runs PUT /api/companies/… with environment, token, scenario ids, and merged company fields, then PUT /api/settings with further_tax_percent and invoice_extra_inputs.

Products tab

Choose default HS codes for the company and optional per-code descriptions that auto-fill when that code is selected on an invoice (same catalogue idea as the invoice page).

• Opening this tab loads HS / item description codes from FBR via the app API (depends on company FBR environment). If the company token is missing, the UI may prompt you to set it on the Company tab first.
• Use the combobox to search and toggle HS codes; selected codes appear as removable badges.
• For each selected code, you can edit narration / description overrides stored in settings; only descriptions that differ from the FBR default are persisted as overrides.
• Save calls PUT /api/settings with company_id, further_tax_percent (shared state with the Company tab—confirm the value if you only save from here), product_hs_codes, product_hs_code_descriptions, and invoice_extra_inputs. It does not update the company record — token, environment, and scenarios are saved only from the Company tab.

Further Tax % and invoice extra inputs load once with GET /api/settings?companyId=… on page load. After changing scenarios, use Testing Scenarios to run sandbox posts. Review changes with your finance team where they affect tax or compliance.

For sales or technical questions, use the contact page or the details in the site footer.