Indotalent Enterprise Kit Documentation

Sales Team

/Main/SalesTeam · Access: Admin, Member, Main · Master Data

The CRM registry of sales teams. Each team stores a name and description plus any number of members maintained inline through the members editor; member rows are stored as Sales Representative records.

What you can do

• Browse, search and page through sales teams (server-side grid).
• Use Create New to register a team and Export XLSX to download the filtered list.
• Maintain team members directly from the team form through the inline members editor.

Key properties

Things worth attention

• Search matches Auto Number, Name or Description.
• Deleting a team is a soft delete that also soft-deletes its member rows.
• Campaigns and Leads reference these records through the Sales Team lookup.

Sales Representative

/Main/SalesRepresentative · Access: Admin, Member, Main · With Lookup

A CRUD screen for sales representative records: the individual salespeople with their job title, employee number and contact details, each assigned to a sales team.

What you can do

• Browse, search and page through sales representative records (server-side grid).
• Use Create New to add a record and Export XLSX to download the currently filtered list.

Key properties

Things worth attention

• Search matches Auto Number, Name, Job Title, Employee Number, Phone Number, Email Address and Description.
• Members are also maintained inline from the Sales Team module through its members editor.

Campaign

/Main/Campaign · Access: Admin, Member, Main · Master-Detail

Manages marketing campaigns with their planning panels: budgets, expenses and leads are edited inline on the campaign Edit page and stored in their own modules, so campaign planning and the standalone Budget, Expense and Lead screens always show the same rows.

What you can do

• Browse, search and page through campaigns (search matches Auto Number, Title, Description, Sales Team or Status).
• Use Create New to register a campaign and Export XLSX to download the filtered list.
• On the Edit page use the embedded Budgets, Expenses and Leads panels to add or change planning rows.

Status lifecycle

Things worth attention

• Panel rows are saved immediately through the Budget, Expense and Lead modules, so they also appear in those modules.
• Deleting a campaign soft-deletes its budget, expense and lead rows.
• Campaign ROI on the CRM dashboard is computed from campaign budgets and expenses.

Budget

/Main/Budget · Access: Admin, Member, Main · With Lookup

A CRUD screen for campaign budget records: a title, budget date, amount and status, each tied to a campaign. Budgets are campaign planning records and are also surfaced inside the Campaign screen.

What you can do

• Browse, search and page through budget records (server-side grid).
• Use Create New to add a record and Export XLSX to download the currently filtered list.

Status lifecycle

Key properties

Things worth attention

• Search matches Auto Number, Title, Status and Description.
• Budgets are edited from both the Budget module and the Campaign planning panel.

Expense

/Main/Expense · Access: Admin, Member, Main · With Lookup

A CRUD screen for campaign expense records: a title, expense date, amount and status, each tied to a campaign. Expenses are campaign spending records and are also surfaced inside the Campaign screen.

What you can do

• Browse, search and page through expense records (server-side grid).
• Use Create New to add a record and Export XLSX to download the currently filtered list.

Status lifecycle

Key properties

Things worth attention

• Search matches Auto Number, Title, Status and Description.
• Expenses are edited from both the Expense module and the Campaign planning panel.

Lead

/Main/Lead · Access: Admin, Member, Main · Master-Detail

The core CRM lead record: a potential deal with its company profile, target and closed amounts, close dates, BANT qualification scores and pipeline stage. Contacts and activities are maintained inline from the lead, and the pipeline stage and closing status drive the CRM dashboard metrics.

What you can do

• Browse, search and page through lead records (server-side grid).
• Use Create New to add a lead and Export XLSX to download the currently filtered list.
• Maintain lead contacts and lead activities from the embedded editors on the lead form.

Pipeline stage

Closing status is one of ClosedLost, ClosedWon or OnProgress; win statistics on the CRM dashboard use the Closed Won status.

Key properties

Things worth attention

• Search covers the title, description, the whole company profile, pipeline stage, closing status and closing note.
• Pipeline stage and closing status drive the dashboard's deal stages and win-rate metrics.
• Contacts and activities are stored in their own modules and also surface there.

Lead Contact

/Main/LeadContact · Access: Admin, Member, Main · With Lookup

A CRUD screen for the people you deal with on a lead: full name, address, contact details and social profiles, each linked to a lead record.

What you can do

• Browse, search and page through lead contact records (server-side grid).
• Use Create New to add a contact and Export XLSX to download the currently filtered list.

Key properties

Things worth attention

• Search matches Auto Number, Full Name, Description, the address and contact fields, and the social profiles.
• Contacts are also maintained inline from the Lead module through its contacts editor.

Lead Activity

/Main/LeadActivity · Access: Admin, Member, Main · With Lookup

A CRUD screen for logged interactions with a lead: calls, e-mails, meetings, events, social media contact and other touchpoints, each with a summary, time window and optional attachment.

What you can do

• Browse, search and page through lead activity records (server-side grid).
• Use Create New to log an activity and Export XLSX to download the currently filtered list.

Key properties

Things worth attention

• Search matches Auto Number, Summary, Type, Attachment Name and Description.
• Activities are also maintained inline from the Lead module through its activities editor.

Todo

/Main/Todo · Access: Admin, Member, Main · Master-Detail

A task-management module for personal or team to-dos. Each to-do captures a title, optional description, priority, category, a schedule (due date and time), numeric progress, a completion state and an optional owner. A to-do is a master record that can hold multiple child checklist items as well as image and file attachments.

What you can do

• Browse, search, sort and page through all to-dos (server-side grid).
• Use Create New to add a to-do and Export XLSX to download the currently filtered list.
• Manage checklist items and attachments on the Create, Edit and Detail screens.

Key properties

Things worth attention

• Global search matches name, description, tags, priority, category, auto number and owner e-mail.
• Status is independent of Progress - update both intentionally.
• Attachments: a to-do can carry checklist items plus image and file attachments.

Todo Dashboard

/Main/TodoDashboard · Access: Admin, Member, Main · Dashboard

A read-only analytics view over the whole to-do dataset. It loads a single payload (summary, priority breakdown, category breakdown, six-month flow and the ten latest to-dos) and renders it as KPI widgets, bar and donut charts, and a recent-records table.

Screen elements

• Four KPI widgets: Total Tasks, Completed, Pending and Overdue, each with a supporting subtitle.
• Tasks by Priority: grouped bars comparing Completed with Pending for Low, Medium, High and Unassigned buckets.
• Completion Status and Category Share donuts, with the completion rate or total count in the center.
• Monthly Task Flow: records created versus records due for the current month and the five preceding months.
• Recent Todos: the ten newest to-dos with priority, category, due date, progress, status, owner and a Detail link.
• Refresh re-fetches the payload without reloading the page.

Things worth attention

• All widgets, charts and the table are built from the same payload, so they always agree on totals.
• Overdue and due-today are evaluated against the server clock in UTC, so day boundaries may differ from local time.
• Soft-deleted records are excluded by the global query filter and never appear in any metric.
• The dashboard is read-only; create, edit, complete and delete actions live in the Todo module.

Customer Category

/ThirdParty/CustomerCategory · Access: Admin, ThirdParty · Master Data

A CRUD screen for customer category records used as a classification lookup. Each record stores an auto number, a name and an optional description.

What you can do

• Browse, search and page through customer category records (server-side grid).
• Use Create New to add a record and Export XLSX to download the currently filtered list.

Key properties

Things worth attention

• Search matches Auto Number, Name and Description.
• The Customer module references these records through the Customer Category lookup.

Customer Group

/ThirdParty/CustomerGroup · Access: Admin, ThirdParty · Master Data

A CRUD screen for customer group lookup records used to categorize customers. Each record stores an auto number, a name and an optional description.

What you can do

• Browse, search and page through customer group records (server-side grid).
• Use Create New to add a group and Export XLSX to download the currently filtered list.

Key properties

Things worth attention

• Search matches Auto Number, Name and Description.
• The Customer module references these records through the Customer Group lookup.

Customer Contact

/ThirdParty/CustomerContact · Access: Admin, ThirdParty · With Lookup

A CRUD screen for customer contact persons: name, job title, phone and e-mail, each linked to a customer record.

What you can do

• Browse, search and page through customer contact records (server-side grid).
• Use Create New to add a contact and Export XLSX to download the currently filtered list.

Key properties

Things worth attention

• Search matches Auto Number, Name, Job Title, Phone Number, Email Address and Description.
• Contacts are also maintained inline from the Customer module through its contacts editor.

Vendor

/ThirdParty/Vendor · Access: Admin, ThirdParty · With Lookup

The CRM registry of vendors. Each vendor stores a profile (address, contact details, social media) plus any number of contact persons maintained inline through the contacts editor and stored as Vendor Contact rows.

What you can do

• Browse, search and page through vendors (server-side grid).
• Use Create New to register a vendor and Export XLSX to download the currently filtered list.
• Maintain contact persons directly in the vendor form through the inline contacts editor.

Key properties

Things worth attention

• Search matches Auto Number, Name, City, Phone, E-mail and the group and category names.
• Deleting a vendor is a soft delete that also soft-deletes its contact rows.
• Purchase documents reference these records through the Vendor lookup.

Vendor Category

/ThirdParty/VendorCategory · Access: Admin, ThirdParty · Master Data

A CRUD screen for vendor category records used as a classification lookup. Each record stores an auto number, a name and an optional description.

What you can do

• Browse, search and page through vendor category records (server-side grid).
• Use Create New to add a record and Export XLSX to download the currently filtered list.

Key properties

Things worth attention

• Search matches Auto Number, Name and Description.
• The Vendor module references these records through the Vendor Category lookup.

Vendor Group

/ThirdParty/VendorGroup · Access: Admin, ThirdParty · Master Data

A CRUD screen for vendor group records used as a classification lookup. Each record stores an auto number, a name and an optional description.

What you can do

• Browse, search and page through vendor group records (server-side grid).
• Use Create New to add a record and Export XLSX to download the currently filtered list.

Key properties

Things worth attention

• Search matches Auto Number, Name and Description.
• The Vendor module references these records through the Vendor Group lookup.

Vendor Contact

/ThirdParty/VendorContact · Access: Admin, ThirdParty · With Lookup

A CRUD screen for vendor contact persons: name, job title, phone and e-mail, each linked to a vendor record.

What you can do

• Browse, search and page through vendor contact records (server-side grid).
• Use Create New to add a contact and Export XLSX to download the currently filtered list.

Key properties

Things worth attention

• Search matches Auto Number, Name, Job Title, Phone Number, Email Address and Description.
• Contacts are also maintained inline from the Vendor module through its contacts editor.

Sales Order

/Sales/SalesOrder · Access: Admin, Sales · Master-Detail

Manages customer orders with priced lines. Lines are real Sales Order Item rows, and every line change recalculates the stored Sub Total, Tax Amount and TOTAL. Confirmed orders are the source that invoices and payment records read their line details from.

What you can do

• Browse, search and page through orders (server-side grid).
• Create the header first, then add lines from the Edit page.
• Print the order as PDF from the Detail page; export the filtered grid to XLSX from the list.

Status lifecycle

Key properties

Things worth attention

• Auto numbers follow the SO/{Year}/{Month}/ sequence.
• Invoices and payments only offer orders with status Confirmed in their reference lookups.
• Pending-payment metrics on the CRM dashboard sum confirmed invoices that are not fully paid.

Delivery Order

/Sales/DeliveryOrder · Access: Admin, Sales · Master-Detail

Manages the Delivery Order inventory document. Lines are stored as Inventory Transaction rows and stock is recalculated through the shared inventory engine: stock leaves the selected physical warehouse and is posted to the CUSTOMER system warehouse.

What you can do

• Browse, search and page through Delivery Order documents (search matches Auto Number, Description and Status).
• Create the header, then add lines from the Edit page; each line picks its own warehouse.
• Print PDF from the Detail page and Export XLSX for the filtered list.

Status lifecycle

Key properties

Things worth attention

• Only lines on documents with status Confirmed count toward stock.
• Each line picks its own warehouse; stock leaves that warehouse to the CUSTOMER system warehouse.
• Sales Returns reference the delivery document they reverse.

Sales Return

/Sales/SalesReturn · Access: Admin, Sales · Master-Detail

Manages the Sales Return inventory document, which brings stock back from the customer. Lines are stored as Inventory Transaction rows (module code SRN) and each line selects the warehouse that receives the returned stock.

What you can do

• Browse, search and page through Sales Return documents (search matches Auto Number, Description and Status).
• Create the header, then add lines from the Edit page.
• Print PDF from the Detail page and Export XLSX for the filtered list.

Status lifecycle

Key properties

Things worth attention

• Only lines on documents with status Confirmed count toward stock.
• Credit notes only offer confirmed sales returns in their reference lookup.

Credit Note

/Sales/CreditNote · Access: Admin, Sales · Master-Detail

Manages credit notes raised from confirmed sales returns. Credit notes store no lines of their own: the lines and totals are always read from the referenced Sales Return, so the adjustment can never drift from the return it credits.

What you can do

• Browse, search and page through credit notes (server-side grid).
• Select a confirmed Sales Return when creating a credit note; its lines and totals are previewed.
• Print the credit note as PDF from the Detail page; export the filtered grid to XLSX from the list.

Status lifecycle

Things worth attention

• Auto numbers follow the CN/{Year}/{Month}/ sequence.
• Only Sales Returns with status Confirmed are offered in the reference lookup.
• Payment records reference confirmed credit notes.

Invoice

/Sales/Invoice · Access: Admin, Sales · Master-Detail

Manages invoices raised from confirmed sales orders. Invoices store no lines of their own: the lines and totals are always read from the referenced Sales Order. The invoice status additionally tracks payment progress with Partial Paid and Full Paid states.

What you can do

• Browse, search and page through invoices (server-side grid).
• Select a confirmed Sales Order when creating an invoice; its lines and totals are previewed.
• Print the invoice as PDF from the Detail page; export the filtered grid to XLSX from the list.

Status lifecycle

Things worth attention

• Auto numbers follow the INV/{Year}/{Month}/ sequence.
• Only Sales Orders with status Confirmed are offered in the reference lookup.
• Recording a payment does not change the invoice status; the status is maintained manually.

Payment Receive

/Sales/PaymentReceive · Access: Admin, Sales · Master-Detail

Records customer payments against confirmed invoices. A payment stores its own amount, date, method and status; the invoice lines and totals shown for reference are always read from the invoice's Sales Order.

What you can do

• Browse, search and page through payment records (server-side grid).
• Select a confirmed Invoice when creating a payment; the suggested amount defaults to the Sales Order total.
• Print the payment receipt as PDF from the Detail page; export the filtered grid to XLSX from the list.

Status lifecycle

Key properties

Things worth attention

• Auto numbers follow the PAY/{Year}/{Month}/ sequence.
• Only invoices with status Confirmed are offered in the reference lookup.
• Payment records do not change the invoice status (status is maintained manually).

Purchase Order

/Purchase/PurchaseOrder · Access: Admin, Purchase · Master-Detail

Manages vendor orders with priced lines. Lines are real Purchase Order Item rows, and every line change recalculates the stored Sub Total, Tax Amount and TOTAL. Confirmed orders are the source that goods receipts and bills read their line details from.

What you can do

• Browse, search and page through orders (server-side grid).
• Create the header first, then add lines from the Edit page.
• Print the order as PDF from the Detail page; export the filtered grid to XLSX from the list.

Status lifecycle

Key properties

Things worth attention

• Auto numbers follow the PO/{Year}/{Month}/ sequence.
• Bills only offer purchase orders with status Confirmed in their reference lookup.

Goods Receive

/Purchase/GoodsReceive · Access: Admin, Purchase · Master-Detail

Manages the Goods Receive inventory document. Lines are stored as Inventory Transaction rows (module code GR) and stock is recalculated through the shared inventory engine: each line receives stock into a physical warehouse from the VENDOR system warehouse.

What you can do

• Browse, search and page through Goods Receive documents (search matches Auto Number, Description and Status).
• Create the header, then add lines from the Edit page; each line picks the receiving warehouse.
• Print PDF from the Detail page and Export XLSX for the filtered list.

Status lifecycle

Key properties

Things worth attention

• Only lines on documents with status Confirmed count toward stock.
• Purchase Returns reference the goods receipt they reverse.

Purchase Return

/Purchase/PurchaseReturn · Access: Admin, Purchase · Master-Detail

Manages the Purchase Return inventory document, which sends stock back to the vendor. Lines are stored as Inventory Transaction rows (module code PRN) and each line selects the warehouse the returned stock leaves.

What you can do

• Browse, search and page through Purchase Return documents (search matches Auto Number, Description and Status).
• Create the header, then add lines from the Edit page.
• Print PDF from the Detail page and Export XLSX for the filtered list.

Status lifecycle

Key properties

Things worth attention

• Only lines on documents with status Confirmed count toward stock.
• Debit notes only offer confirmed purchase returns in their reference lookup.

Debit Note

/Purchase/DebitNote · Access: Admin, Purchase · Master-Detail

Manages debit notes raised from confirmed purchase returns. Debit notes store no lines of their own: the lines and totals are always read from the referenced Purchase Return, so the adjustment can never drift from the return it debits.

What you can do

• Browse, search and page through debit notes (server-side grid).
• Select a confirmed Purchase Return when creating a debit note; its lines and totals are previewed.
• Print the debit note as PDF from the Detail page; export the filtered grid to XLSX from the list.

Status lifecycle

Things worth attention

• Auto numbers follow the DN/{Year}/{Month}/ sequence.
• Only Purchase Returns with status Confirmed are offered in the reference lookup.
• Payment records reference confirmed debit notes.

Bill

/Purchase/Bill · Access: Admin, Purchase · Master-Detail

Manages bills raised from confirmed purchase orders. Bills store no lines of their own: the lines and totals are always read from the referenced Purchase Order. The bill status additionally tracks payment progress with Partial Paid and Full Paid states.

What you can do

• Browse, search and page through bills (server-side grid).
• Select a confirmed Purchase Order when creating a bill; its lines and totals are previewed.
• Print the bill as PDF from the Detail page; export the filtered grid to XLSX from the list.

Status lifecycle

Things worth attention

• Auto numbers follow the BILL/{Year}/{Month}/ sequence.
• Only Purchase Orders with status Confirmed are offered in the reference lookup.
• Recording a payment does not change the bill status; the status is maintained manually.

Payment Disburse

/Purchase/PaymentDisburse · Access: Admin, Purchase · Master-Detail

Records payments issued to vendors against confirmed bills. A payment stores its own amount, date, method and status; the bill lines and totals shown for reference are always read from the bill's Purchase Order.

What you can do

• Browse, search and page through payment records (server-side grid).
• Select a confirmed Bill when creating a payment; the suggested amount defaults to the order total.
• Print the payment voucher as PDF from the Detail page; export the filtered grid to XLSX from the list.

Status lifecycle

Key properties

Things worth attention

• Auto numbers follow the DISB/{Year}/{Month}/ sequence.
• Only bills with status Confirmed are offered in the reference lookup.
• Payment records do not change the bill status (status is maintained manually).

Product Group

/Inventory/ProductGroup · Access: Admin, Inventory · Master Data

A CRUD screen for product group records used to categorize the catalog. Each record stores an auto number, a name and an optional description.

What you can do

• Browse, search and page through product group records (server-side grid).
• Use Create New to add a record and Export XLSX to download the currently filtered list.

Key properties

Things worth attention

• Search matches Auto Number, Name and Description.
• The Product module references these records through the Product Group lookup.

Product

/Inventory/Product · Access: Admin, Inventory · With Lookup

The product catalog. Each record stores an auto number, a name, a unit price that acts as the default price on document lines, a physical-product flag, and lookups to the unit measure and product group.

What you can do

• Browse, search and page through product records (server-side grid).
• Use Create New to add a product and Export XLSX to download the currently filtered list.

Key properties

Things worth attention

• Search matches Auto Number, Name and Description.
• Products are referenced by sales and purchase document lines and by inventory transactions; only physical products appear in stock reports.

Warehouse

/Inventory/Warehouse · Access: Admin, Inventory · Master Data

Manages the warehouses used by the stock engine. Beside your own physical warehouses, the system seeds six virtual system warehouses that model the counterparty of each stock movement.

What you can do

• Browse, search and page through warehouse records (server-side grid).
• Use Create New to add a physical warehouse and Export XLSX to download the currently filtered list.

Key properties

Things worth attention

• Six system warehouses are seeded automatically: CUSTOMER, VENDOR, TRANSIT, STOCK_COUNT, ADJUSTMENT and SCRAPPING.
• Inventory documents move stock between physical warehouses and these system warehouses.
• Stock reports exclude system warehouses by design.

Transfer Out

/Inventory/TransferOut · Access: Admin, Inventory · Master-Detail

Manages the Transfer Out inventory document. Lines are stored as Inventory Transaction rows (module code TO-OUT), and adding, editing or deleting a line posts its transaction immediately so stock stays correct.

What you can do

• Browse, search and page through Transfer Out documents (search matches Auto Number, Description and Status).
• Create the header with its source and destination warehouses, then add lines from the Edit page.
• Print PDF from the Detail page and Export XLSX for the filtered list.

Status lifecycle

Key properties

Things worth attention

• Only lines on documents with status Confirmed count toward stock.
• Transfer In documents are created against a confirmed Transfer Out.

Transfer In

/Inventory/TransferIn · Access: Admin, Inventory · Master-Detail

Manages the Transfer In inventory document, which receives stock at the destination warehouse. Lines are stored as Inventory Transaction rows (module code TO-IN) and the destination warehouse follows the referenced Transfer Out document.

What you can do

• Browse, search and page through Transfer In documents (search matches Auto Number, Description and Status).
• Create the header against a Transfer Out document, then add lines from the Edit page.
• Print PDF from the Detail page and Export XLSX for the filtered list.

Status lifecycle

Key properties

Things worth attention

• Only lines on documents with status Confirmed count toward stock.
• Transfers count once the outbound and inbound documents are both confirmed.

Positive Adjustment

/Inventory/PositiveAdjustment · Access: Admin, Inventory · Master-Detail

Manages the Positive Adjustment inventory document, which increases stock. Lines are stored as Inventory Transaction rows (module code ADJ+). The document header has no warehouse, so each line selects its own warehouse.

What you can do

• Browse, search and page through Positive Adjustment documents (search matches Auto Number, Description and Status).
• Create the header, then add lines from the Edit page.
• Print PDF from the Detail page and Export XLSX for the filtered list.

Status lifecycle

Key properties

Things worth attention

• Each line selects its own warehouse because the document header has no warehouse.
• Only lines on documents with status Confirmed count toward stock.

Negative Adjustment

/Inventory/NegativeAdjustment · Access: Admin, Inventory · Master-Detail

Manages the Negative Adjustment inventory document, which decreases stock. Lines are stored as Inventory Transaction rows (module code ADJ-); the movement is stored as an absolute value and the direction comes from the module itself.

What you can do

• Browse, search and page through Negative Adjustment documents (search matches Auto Number, Description and Status).
• Create the header, then add lines from the Edit page.
• Print PDF from the Detail page and Export XLSX for the filtered list.

Status lifecycle

Key properties

Things worth attention

• Movement is stored as an absolute value; the direction comes from the module.
• Only lines on documents with status Confirmed count toward stock.

Scrapping

/Inventory/Scrapping · Access: Admin, Inventory · Master-Detail

Manages the Scrapping inventory document, which writes stock off. Lines are stored as Inventory Transaction rows (module code SCRP); the movement is stored as an absolute value and the direction comes from the module.

What you can do

• Browse, search and page through Scrapping documents (search matches Auto Number, Description and Status).
• Create the header with its warehouse, then add lines from the Edit page.
• Print PDF from the Detail page and Export XLSX for the filtered list.

Status lifecycle

Key properties

Things worth attention

• Movement is stored as an absolute value; the direction comes from the module.
• Only lines on documents with status Confirmed count toward stock.

Stock Count

/Inventory/StockCount · Access: Admin, Inventory · Master-Detail

Manages the Stock Count inventory document, which reconciles physical counts with system stock. Lines are stored as Inventory Transaction rows (module code COUNT): the system quantity is computed from confirmed stock and the delta becomes the posted movement.

What you can do

• Browse, search and page through Stock Count documents (search matches Auto Number, Description and Status).
• Create the header with its warehouse, then record counted quantities on the lines.
• Print PDF from the Detail page and Export XLSX for the filtered list.

Status lifecycle

Key properties

Things worth attention

• System quantity is computed from confirmed stock; the delta becomes the posted movement.
• Only lines on documents with status Confirmed count toward stock.

Stock Report

/Inventory/StockReport · Access: Admin, Inventory · Report

Shows current on-hand stock per physical warehouse and product. Only Confirmed inventory transactions count, and system warehouses are excluded so the figures reflect real inventory.

What you can do

• Check the live stock position for every product in every physical warehouse.
• Search by warehouse, product number or product name; Export XLSX downloads the filtered report.

Key columns

Things worth attention

• Draft or cancelled documents do not affect this report.
• Transfers count once the outbound and inbound documents are confirmed.

Movement Report

/Inventory/MovementReport · Access: Admin, Inventory · Report

Summarizes confirmed stock movements per warehouse and product, split into one column per document type: ADJ+, ADJ-, COUNT, DO, GR, PRN, SCRP, SRN, TO-IN and TO-OUT.

What you can do

• Understand where stock changed and by which document type.
• Search by warehouse, product number or product name; Export XLSX downloads the filtered grid.

Things worth attention

• Only Confirmed transactions count; system warehouses are excluded.
• Grand Total is the sum of all module columns for the row.

Transaction Report

/Inventory/TransactionReport · Access: Admin, Inventory · Report

Lists every confirmed inventory transaction with its document reference, product, warehouse routing, signed movement and resulting stock value - the audit trail behind the Stock and Movement reports.

What you can do

• Trace exactly which document produced a stock movement and when.
• Search by auto number, module code, module number, warehouse or product; Export XLSX downloads the filtered grid.

Key columns

Things worth attention

• Only Confirmed transactions appear.
• Line rows are created instantly from their document editors; deleting a line removes it from this report.

Booking Resource

/Utilities/BookingResource · Access: Admin, Utilities · With Lookup

A CRUD screen for bookable resources: rooms, equipment or people that bookings can be scheduled against. Each resource belongs to a booking group.

What you can do

• Browse, search and page through booking resource records (server-side grid).
• Use Create New to add a resource and Export XLSX to download the currently filtered list.

Key properties

Things worth attention

• Search matches Auto Number, Name and Description.
• Bookings reference these resources through the Booking Resource lookup.

Booking

/Utilities/Booking · Access: Admin, Utilities · With Lookup

A CRUD screen for booking records. Each booking stores scheduler data - subject, resource, start and end times, all-day flag and recurrence fields - against a booking resource. The template has no calendar component, so bookings are managed as rich CRUD records with all scheduler fields preserved.

What you can do

• Browse, search and page through booking records (server-side grid).
• Use Create New to add a booking and Export XLSX to download the currently filtered list.

Status lifecycle

Key properties

Things worth attention

• Search matches Auto Number, Subject, Status, Location, timezones, Description and the recurrence fields.
• The V4 template has no calendar component; scheduling data is kept complete so a calendar view can be layered on later.

Program Manager

/Utilities/ProgramManager · Access: Admin, Utilities · With Lookup

A CRUD screen for tracked work items: each record has a title, status, priority, summary and a reference to the program resource that carries it.

What you can do

• Browse, search and page through program manager records (server-side grid).
• Use Create New to add a record and Export XLSX to download the currently filtered list.

Status and priority

Key properties

Things worth attention

• Search matches Auto Number, Title, Status, Priority and Summary.
• Program Manager records follow the shared AutoNumber rules on every path (runtime and seeding).

Program Resource

/Utilities/ProgramManagerResource · Access: Admin, Utilities · Master Data

A CRUD screen for program resource records: the people or teams that program manager items are assigned to. Each record stores an auto number, a name and an optional description.

What you can do

• Browse, search and page through program resource records (server-side grid).
• Use Create New to add a record and Export XLSX to download the currently filtered list.

Key properties

Things worth attention

• Search matches Auto Number, Name and Description.
• Program Manager records reference these resources through the Program Resource lookup.

Payment Method

/Utilities/PaymentMethod · Access: Admin, Utilities · Master Data

A CRUD screen for payment method records used when recording money in and out. Five methods are seeded by default: Credit Card, Debit Card, Bank Transfer, PayPal and Cash.

What you can do

• Browse, search and page through payment method records (server-side grid).
• Use Create New to add a method and Export XLSX to download the currently filtered list.

Key properties

Things worth attention

• Search matches Auto Number, Name and Description.
• Payment Receive and Payment Disburse reference these records through the Payment Method lookup.

Role

/Admin/Role · Access: Admin · Identity

A read-only list of the application's roles. Roles gate which modules and menus appear: the Main area is available to Member/Admin, the Admin area requires Member and Admin together, and AI requires Admin or AI.

What you can do

• Browse and search roles (search matches the role name); rows are always ordered A-Z.
• Open the Detail view for a role and export the list to XLSX.

Things worth attention

• There is no create, edit or delete path in this module - it is browse-and-detail only.
• Eleven roles are seeded: Guest, Member, Admin, AI, SuperAdmin, Main, Sales, Purchase, Inventory, ThirdParty and Utilities.
• A user's role set is managed from Admin → User → Roles, where assignment replaces the whole set.

Tax

/Admin/Tax · Access: Admin · Master Data

An admin CRUD screen for tax-rate lookups used as reference/master data. Each record carries an auto number, a unique code, a name, a percentage and an optional description. Document lines read their tax percentage from the selected Tax record.

What you can do

• Browse, search and page through tax records (server-side grid).
• Use Create New to add a tax and Export XLSX to download the currently filtered list.

Key properties

Things worth attention

• Search matches Code or Name; codes must be unique.
• Sales and purchase document lines recalculate their totals when the selected tax changes.

Country

/Admin/Country · Access: Admin · Master Data

An admin CRUD screen for country lookup records used as reference data (for example, the Currency module links to countries). Each record stores an auto number, a unique code, a name and an optional description.

What you can do

• Browse, search and page through country records (server-side grid).
• Use Create New to add a country and Export XLSX to download the currently filtered list.

Key properties

Things worth attention

• Search matches Code, Name and Description.
• Countries are seeded: US, EU, GB, ID, SG, IN, AU and CN.
• The Currency module references these records.

Currency

/Admin/Currency · Access: Admin · With Lookup

An admin CRUD screen for currencies, each optionally linked to a country. Records carry an auto number, a unique code, a name, a symbol, an optional country reference and a description.

What you can do

• Browse, search and page through currency records (server-side grid).
• Use Create New to add a currency and Export XLSX to download the currently filtered list.

Key properties

Things worth attention

• Search matches Code, Name or the linked Country name; codes must be unique.
• Seeded currencies correspond to the seeded countries: USD, EUR, GBP, IDR, SGD, INR, AUD and CNY.
• Companies reference currencies; the Company profile requires one.

Auto Number Sequence

/Admin/AutoNumberSequence · Access: Admin · Configuration

A maintenance screen for the internal per-entity, per-year counters that generate the stable Auto Number values on auto-numbered records (documents, tax, country, currency, company and more). Each row describes one entity/year bucket.

What you can do

• Browse the counters and open Detail or Edit to inspect or adjust a sequence.
• Use Create New to add a sequence manually; rows are normally created automatically on first use.
• Export the list to XLSX.

Key properties

How it works

When a new auto-numbered record is saved without an Auto Number, the system derives a short code from the entity name (first three consonants, uppercased), forms a prefix template such as TAX/2026/, looks up (or lazily creates) the matching sequence row, increments Current Sequence, and formats prefix + padded value + suffix. Editing a row affects only numbers generated afterward. See AutoNumber Generation for the runtime flow.

Things worth attention

• Search matches Entity Name only.
• Do not lower Current Sequence while records are still being created, or generated numbers may collide.
• Rows exist only for entity/year combinations that have actually issued a number.

Company

/Admin/Company · Access: Admin · Configuration

The organization master record used across the app. The UI is effectively single-record: the data model allows many rows but there is no create path, and each tenant is provisioned with one default record named after the tenant (fallback Company) with the default flag set.

What you can do

• Locate the company record in the searchable list.
• Use Detail and Edit to update the profile data; Export XLSX downloads the list.

Key properties

Things worth attention

• Search matches Name, Tax ID, City, Phone or E-mail (not the currency name).
• There is no Create or Delete path in this module.

Branch

/Admin/Branch · Access: Admin · Configuration

A CRUD screen for the branch master. Branches are the organizational scoping unit of the application: every branch-scoped document and operational master carries a BranchId and the forms expose a Branch selector. A protected Head Office branch is seeded per tenant and cannot be deleted.

What you can do

• Browse, search and page through branch records (server-side grid).
• Use Create New to add a branch and Export XLSX to download the currently filtered list.
• Select a row to reveal Detail and Edit; the Delete action is blocked for Head Office and for branches still in use.

Key properties

Things worth attention

• Search matches Auto Number, Name and Description.
• Deleting a branch is blocked while any document or operational master still references it; Head Office is always blocked.
• Branches are tenant-scoped: each workspace has its own Head Office and its own branch list. See Branch (Multi-Branch) for the scoping rules and the per-tenant backfill.

Tenant User

/SuperAdmin/TenantUser · Access: SuperAdmin · Identity

Maps system users to tenant workspaces. A user can belong to several tenants and picks one after signing in; this mapping controls which workspaces are offered at selection time. A pair of tenant and user can only be mapped once.

What you can do

• Browse, search and page through user-to-tenant mappings (search matches Tenant, System User or Summary).
• Use Create New to grant a user access to a tenant; Edit to change the tenant, user, summary or Is Active.
• Select a row to reveal the user actions: Roles, Avatar, Password, Email and Params (they link to the System User screens).
• Export XLSX to download the currently filtered list.

Things worth attention

• Switch Is Active off to suspend access without deleting the mapping.
• Removing a mapping is a soft delete; the user simply no longer sees that tenant at selection time.
• Every user holding the SuperAdmin role is mapped automatically to every tenant, including new ones.
• Newly registered users receive their own default tenant workspace mapping automatically (see the Multitenant section).

System User

/SuperAdmin/User · Access: SuperAdmin · Identity

The global counterpart of the tenant-scoped Admin User module. It manages the application's sign-in accounts (ASP.NET Identity ApplicationUser records) across every tenant: username, e-mail, full name, avatar, e-mail confirmation state, assigned roles, password and profile parameters. Unlike the Admin module, the list shows all system users, whether or not they are mapped to a tenant.

What you can do

• Browse the paged, searchable list of accounts (server-side grid).
• Click a row to reveal the row actions: Detail, Edit, Roles, Avatar, Password, Email and Params.
• Use Create New to add an account and Export XLSX to download the currently filtered list.

Key properties

Things worth attention

• Search matches Username, Email or Full Name only, across the whole system.
• Create New makes the account pre-confirmed and active, and returns a randomly generated 12-character password to hand over securely.
• The optional Assign to Tenant lookup maps the new account to a tenant in the same submit; leave it empty to create a user without any tenant mapping.
• Roles are not set at creation; use the Roles action, where assignment replaces the user's whole role set.
• Eleven roles are seeded: Guest, Member, Admin, AI, SuperAdmin, Main, Sales, Purchase, Inventory, ThirdParty and Utilities.
• The default administrator (admin@root.com) is protected from role, e-mail and password changes in demo mode.
• Params edits personal info, address, social media and "other information" stored directly on the user record.
• Tenant mappings themselves are managed in the Tenant User module; see Multitenant for the sign-in and selection flow.

Health Check

/SuperAdmin/HealthCheck · Access: SuperAdmin · Dashboard

The System Monitoring Dashboard queries the public /health endpoint (overall banner plus one card per registered check) and pulls an in-memory traffic snapshot from the SuperAdmin-only /api/ops/metrics endpoint. See Health Checks and System Monitoring for the underlying endpoints.

Health checks and traffic metrics

• Database - can the app connect to its database via EF Core.
• Storage - the wwwroot/data folder exists and has free space; under 100 MB free is reported as Degraded. Both checks are toggleable under HealthCheckSettings.
• Traffic is counted in memory by middleware; health probes, static assets and the metrics endpoint itself are excluded.
• The rolling window (default 5 minutes) and recent-request cap (default 200) are configurable under OpsMetricsSettings.
• Latency percentiles (P95/P99) are approximated from a bounded per-minute histogram, so memory stays flat under load.

Screen elements

• Overall status banner (Healthy, Degraded, Unhealthy or Status Unknown on fetch failure).
• One card per check with colored status badge, duration and description; an application card with app name, version, environment, uptime and server time.
• Traffic card with request count, 2xx/5xx counts, error rate, avg/P95/P99 latency and per-status-family counts.
• Recent endpoints list with method, path, status, duration and time; slow calls (1 second or more) are highlighted.
• Refresh reloads the page to re-run the checks and pull a fresh metrics snapshot.

Things worth attention

• If the traffic section reports an access error, the signed-in account does not hold the SuperAdmin role.
• Traffic numbers reset whenever the web process restarts (the store is in-memory only).

Serilog

/SuperAdmin/Serilog · Access: SuperAdmin · Utility

A Super Admin UI for the application's Serilog text log files (rolling daily), stored under wwwroot/data/serilog with the file pattern log-yyyyMMdd.txt. Logging records Information and above, and the newest file is listed first. See Logging for the pipeline configuration.

What you can do

• Browse the log files and search by file name.
• Select a row to reveal Download (save the file) and Detail (read its content).
• Export the file list to XLSX.

Key properties

Things worth attention

• File cleanup is automatic: a daily background job deletes log files older than 3 days - export or download anything you need before cleanup runs.
• Each line follows the configured output template and starts with a timestamp and level.

System File

/SuperAdmin/SystemFile · Access: SuperAdmin · Utility

A read-only viewer for deployment and configuration files served from the application content root: App Settings (appsettings.json), Dockerfile and Docker Compose (docker-compose.yaml). Nothing here can be edited. See Application Name for how appsettings.json drives the UI, and Multi-Database for the connection strings shown in these files.

What you can do

• Open the three screens: App Settings (/SuperAdmin/SystemFile/AppSettings), Dockerfile (/SuperAdmin/SystemFile/Dockerfile) and Docker Compose (/SuperAdmin/SystemFile/DockerCompose).
• Read each file with sensitive values masked by default: SecretKey, Password, ApiKey, ApiSecret, ConnectionString, MessagingSenderId and AppId for App Settings; the database connection string and SMTP password for Docker Compose.
• Use Reveal (App Settings and Docker Compose only) to show raw values after a confirmation prompt, Mask Again to hide them, Copy to copy the displayed content, and Refresh to re-read the file from disk.

Things worth attention

• When demo mode is active, a reveal request is accepted but the server still returns masked content, so raw secrets are never sent.
• Files are resolved from a fixed whitelist; no path can be supplied by the client.
• Responses are sent with Cache-Control: no-store so secrets are not cached by the browser.

Job Dashboard

/SuperAdmin/JobDashboard · Access: SuperAdmin · Utility

The entry point to the external Hangfire dashboard at /hangfire. The page shows a small card and redirects automatically; the Hangfire dashboard itself is mounted outside the VSA module pattern, so it has no Module Info drawer.

What you can do

• Open the Hangfire dashboard to inspect recurring, fire-and-forget and delayed jobs, their history and failures.
• Use the manual Open Hangfire Dashboard button if the automatic redirect did not run.

Things worth attention

• The dashboard is guarded by the SuperAdmin role (Hangfire authorization filter) - other accounts cannot open it.
• The recurring serilog-cleanup job (daily at midnight) appears here; see Background Jobs for the scheduled jobs it manages.