Incoming Inventory - Acosys Documentation

Used By

Operational users and finance team

transaction

Division, Invoice

When users need to create, review, or update Incoming Inventory.
When the transaction needs to become part of reports, balances, journals, or the next workflow.
When existing data needs correction because policies, accounts, prices, contacts, or operating rules have changed.

Make sure the user has access to this menu and the related reference data has already been prepared.
Check required fields first, especially codes, names, dates, accounts, customers, suppliers, products, divisions, or departments.
If the form uses active status, confirm the status before saving so the data appears in the correct selections.

Open Form Products / Incoming Inventory.
Create a new record, or select an existing record when the data needs to be corrected.
Fill in the required fields and complete supporting information that helps search, reporting, or transaction processing.
Review detail lines, totals, payment information, taxes, discounts, and notes before saving.
Click Save. If the application shows a validation message, follow the message until the data is saved successfully.

Field	User Explanation	Status
Division `division`	Business unit or branch related to this record. Choose the correct division before saving.	Required
Invoice `id`	Unique code used to identify Incoming Inventory. Use a consistent pattern so users can search and sort the data easily.	Required
Date `transdate`	Date used for recording, filtering, or reporting this data. Check the period before saving.	Required
Time `transtime`	Time used to distinguish entries that happen on the same date.	Required
Department `department`	Department, warehouse, work location, or cost center related to this record.	Required
Offset Account `accountid`	Account used for journals and financial reporting. Check the account before saving.	Required

If the form contains detail lines, each line affects totals, balances, stock, journals, or follow-up documents.
Audit fields are filled in automatically by the application and help support teams trace changes.

The transaction can be used by reports, audit checks, and the next related process.
Changes are normally used for new activity. Historical documents remain available for review.
If required data is incomplete or inconsistent, the application rejects the save and shows a validation message.

Data cannot be saved: complete required fields and read the validation message shown by the application.
Data does not appear in selection or search: check active status, access rights, filters, and the search keyword.
Duplicate code or name: use the existing record when it should be corrected, or use a different code for a new record.
Report values do not match: recheck reference data, accounts, dates, transaction status, and related filters.

The list below summarizes the fields available in this form. Field labels follow the English UI language file used by the application.

Field	User Explanation	Status
Division `division`	Business unit or branch related to this record. Choose the correct division before saving.	Required
Invoice `id`	Unique code used to identify Incoming Inventory. Use a consistent pattern so users can search and sort the data easily.	Required
Date `transdate`	Date used for recording, filtering, or reporting this data. Check the period before saving.	Required
Time `transtime`	Time used to distinguish entries that happen on the same date.	Required
Department `department`	Department, warehouse, work location, or cost center related to this record.	Required
Offset Account `accountid`	Account used for journals and financial reporting. Check the account before saving.	Required
Incoming Inventory `inventoryindetail`	Incoming Inventory stores information needed by Incoming Inventory. Fill it in according to the company data standard.	Required
Last Updated `updatetimestamp`	Audit timestamp filled in automatically by the application.	Optional
Notes `memo`	Additional explanation for users who need context when reviewing this record.	Optional
Created By `usercreate`	Audit information filled in automatically when the record is created.	Optional
Updated By `useredit`	Audit information filled in automatically when the record is updated.	Optional