Transaction
This documentation is incomplete.
An AR invoice is a document issued by a business specifying the goods and services sold to a customer. In inoERP, you can create an invoice using the transaction screen. You can also use the transaction screen to create Debit Memos and Credit Memos.
You can create a transaction from a sales order/delivery/project. You can also create a transaction by manually entering all the required information such as customer, items/product description, quantities, date, etc. A transaction consists of
- Header
- Line
- Detail
Header
A transaction header contains the customer, business unit, currency-related information. When converting a transaction to an Invoice, the system copies all the header level information to the destination document.
To view/create/update a transaction, navigate to the "transaction" search screen from your dashboard/favorite.
Enter the organization/transaction details or any other criteria in the search form and click on the search button to view an existing transaction.
Click on create a new button to create a new transaction; by manually entering all the information,
Copy an existing transaction to a new transaction is always better than manually entering all the data to create a new transaction.
The application lets you update all the details before confirmation; you can configure which fields are view-only after the confirmation.
Business Org: Select a business organization from the list. The system shows only that business org to which you have access. You can either select the business org from the list or enter the business org code. The system will default all the other fields based on the chosen business org. The business org is a mandatory field and can't be changed after the document is saved. If you change the business org, the system will remove the values from all the other fields.
If you don't enter organization/customer details, the system will show you all the transactions. If your organization has configured to make any field mandatory for search, then you have to enter those fields to search transactions.
The application will fetch all the server data and take you to the search result screen. The search result screen looks a bit different on desktop and mobile devices.
Customer Name: Customer name is a mandatory field in the header. Select a customer name from the drop-down list. The system defaults customer number, customer id, etc., from the customer name. You can also enter the customer number, customer id, etc., and the system will default the customer name.
Customer Site Name: Customer site name is also a mandatory field in the header. Select a customer site name from the drop-down list. The system defaults the customer site number, customer site id, etc., from the customer site name. You can also enter the customer site number, customer site id, etc., and the system will default the customer site name. If you select a customer site name before entering a customer name in the header, the system will default the customer name from the selected site name. The system also defaults other information (such as payment terms, document currency, etc.) from the customer site.
To view the search result in a table format, click on the table icon available on the bottom left corner.
To open a specific transaction, click on the menu of that record, and click on view/fetch & view.
You can also click on the expand icon against any item on the search result screen to view the transaction header details such as transaction number, quantities, start date, status, etc.
Doc Status: A read-only field showing the document's current status. The value is maintained by the system and changed depending on actions and transactions on the record. The system will default the document status to "Draft" for a new document.
Accounting Status: A read-only field showing the current accounting status of the document. The value is maintained by the system and changed depending on actions and transactions on the record. After accounting is completed, the system will change the document status to "accounting_completed." for a new document, the system will default the document status to "not_accounted."
The system will fetch all the data related to the selected transaction. The transaction details are shown either right to the search result screen or on a separate screen, depending on the device size.
Scroll left, right, up, down to view all the details. The transaction line and details are shown in a separate tab. The default configuration shows fields in various functional groups such as
- Finance
- Entity
- Reference
- Data
- Control
- Etc
You can configure the application to show which fields should be shown under which group. You can also create new groups as per your business requirements.
All Fields
Name | Sequence | Label | InputType | Field Group |
---|---|---|---|---|
10 | vvBuOrg | Bu Org | deferredSelect | ENTITY |
10 | vvBuOrgCode | Bu Org Code | deferredSelect | ENTITY |
20 | vvCustomerNumber | Customer Number | deferredSelect | DATA |
30 | vvCustomerName | Customer Name | deferredSelect | ENTITY |
40 | vvCustomerSiteNumber | Customer Site Number | deferredSelect | DATA |
50 | vvCustomerSiteName | Customer Site Name | deferredSelect | ENTITY |
60 | vvPaymentTerm | Payment Term | deferredSelect | FINANCE |
70 | vvPaymentTermDescription | Payment Term Description | InputType.textField | FINANCE |
80 | vvShipToAddressName | Ship To Address Name | deferredSelect | ENTITY |
90 | vvShipToAddress | Ship To Address | deferredSelect | ENTITY |
100 | vvShipToCountry | Ship To Country | deferredSelect | ENTITY |
110 | vvShipToPostalCode | Ship To Postal Code | deferredSelect | ENTITY |
120 | vvShipToEmail | Ship To Email | deferredSelect | ENTITY |
130 | vvShipToPhone | Ship To Phone | deferredSelect | ENTITY |
140 | vvBillToAddressName | Bill To Address Name | deferredSelect | PLANNING |
150 | vvBillToAddress | Bill To Address | deferredSelect | PLANNING |
160 | vvBillToCountry | Bill To Country | deferredSelect | PLANNING |
170 | vvBillToPostalCode | Bill To Postal Code | deferredSelect | PLANNING |
180 | vvBillToEmail | Bill To Email | deferredSelect | PLANNING |
190 | vvBillToPhone | Bill To Phone | deferredSelect | PLANNING |
200 | vvHeaderAmount | Header Amount | InputType.textField | FINANCE |
210 | vvHeaderTaxAmount | Header Tax Amount | InputType.textField | FINANCE |
220 | vvHeaderDiscountAmount | Header Discount Amount | InputType.textField | FINANCE |
230 | sdSoHeaderId | Sd So Header Id | InputType.number | REFERENCE |
240 | srcEntityName | Src Entity Name | deferredSelect | DEFAULT |
250 | srcEntityId | Src Entity Id | InputType.textField | REFERENCE |
260 | buOrgId | Bu Org Id | deferredSelect | REFERENCE |
270 | documentType | Document Type | InputType.select | CONTROL |
280 | soNumber | So Number | InputType.textField | DATA |
290 | arCustomerId | Ar Customer Id | deferredSelect | REFERENCE |
300 | arCustomerSiteId | Ar Customer Site Id | deferredSelect | REFERENCE |
310 | hrEmployeeId | Hr Employee Id | InputType.number | REFERENCE |
320 | description | Description | InputType.textField | DEFAULT |
330 | shipToId | Ship To Id | deferredSelect | REFERENCE |
340 | billToId | Bill To Id | deferredSelect | PLANNING |
350 | priceListHeaderId | Price List Header Id | InputType.number | REFERENCE |
360 | prePaymentAmount | Pre Payment Amount | InputType.textField | FINANCE |
370 | docCurrency | Doc Currency | deferredSelect | FINANCE |
380 | paymentTermId | Payment Term Id | deferredSelect | REFERENCE |
390 | paymentTermDate | Payment Term Date | InputType.date | DATE |
400 | exchangeRateType | Exchange Rate Type | deferredSelect | CONTROL |
410 | exchangeRate | Exchange Rate | InputType.textField | FINANCE |
420 | orderSourceType | Order Source Type | InputType.select | CONTROL |
430 | orderReferenceTable | Order Reference Table | InputType.textField | REFERENCE |
440 | orderReferenceId | Order Reference Id | InputType.number | REFERENCE |
450 | docStatus | Doc Status | InputType.select | CONTROL |
460 | referenceType | Reference Type | InputType.textField | CONTROL |
470 | referenceKeyName | Reference Key Name | InputType.textField | REFERENCE |
480 | referenceKeyValue | Reference Key Value | InputType.number | REFERENCE |
490 | approvalStatus | Approval Status | InputType.select | CONTROL |
540 | revEnabledCb | Rev Enabled Cb | InputType.switchField | DEFAULT |
550 | revNumber | Rev Number | InputType.number | DATA |
560 | glAcProfileHeaderId | Gl Ac Profile Header Id | deferredSelect | REFERENCE |
5500 | createdBy | Created By | InputType.textField | REFERENCE |
5510 | creationDate | Creation Date | InputType.dateTime | REFERENCE |
5520 | lastUpdatedBy | Last Updated By | InputType.textField | REFERENCE |
5530 | lastUpdateDate | Last Update Date | InputType.dateTime | REFERENCE |
Lines
You can add multiple lines to each transaction header. Each transaction line contains an item, UOM, product description, quantity, sold from inventory organization, line number, unit price, etc.
Navigate to the lines tab to view/add/update lines.
Click on the add new entity to add a new line. If a line already exists, click on copy entity to copy all the details.
You can enable/disable fields allowed to be copied in the menu configuration.
Line Number: Line number is a mandatory field. Enter a numeric value for the line
Line Quantity: Line quantity is a mandatory field. Enter a numeric value for the line quantity. The system uses the line quantity to create detail lines. System multiplies the line quantity with the unit price to calculate journal line amounts.
The entity group shows information related to business organization, customer, etc.
The reference groups show various ids for reference only. You don't need to enter any information in this section. When you save a transaction for the first time, the system will auto-populate the newly created header id and line ids.
In the finance section, enter the unit price. The system calculates the line price by multiplying the unit price with quantity. The header price is the sum of all the line prices. You don't need to enter any price at the transaction header.
Scroll left, right, up, and down view all other fields.
Enter all the other fields and click on the save button to save the transaction. The app will post all the data to the server and will show the messages returned from the server.
All Fields
Name | Sequence | Label | InputType | Field Group |
---|---|---|---|---|
10 | vvOrgCode | Org Code | deferredSelect | ENTITY |
10 | vvItemNumber | Item Number | deferredSelect | DEFAULT |
20 | vvUomCode | Uom Code | deferredSelect | DEFAULT |
30 | vvUomDescription | Uom Description | deferredSelect | DEFAULT |
40 | vvItemStatus | Item Status | deferredSelect | CONTROL |
50 | vvShipToAddressName | Ship To Address Name | deferredSelect | ENTITY |
60 | vvShipToAddress | Ship To Address | deferredSelect | ENTITY |
70 | vvShipToCountry | Ship To Country | deferredSelect | ENTITY |
80 | vvShipToPostalCode | Ship To Postal Code | deferredSelect | ENTITY |
90 | vvShipToEmail | Ship To Email | deferredSelect | ENTITY |
100 | vvShipToPhone | Ship To Phone | deferredSelect | ENTITY |
110 | vvBillToAddressName | Bill To Address Name | deferredSelect | PLANNING |
120 | vvBillToAddress | Bill To Address | deferredSelect | PLANNING |
130 | vvBillToCountry | Bill To Country | deferredSelect | PLANNING |
140 | vvBillToPostalCode | Bill To Postal Code | deferredSelect | PLANNING |
150 | vvBillToEmail | Bill To Email | deferredSelect | PLANNING |
160 | vvBillToPhone | Bill To Phone | deferredSelect | PLANNING |
170 | vvDiscountedLinePrice | Discounted Line Price | InputType.textField | FINANCE |
180 | vvTaxCalculationMethod | Tax Calculation Method | deferredSelect | FINANCE |
190 | vvTaxPercentage | Tax Percentage | deferredSelect | FINANCE |
200 | vvTaxTaxAmount | Tax Tax Amount | InputType.textField | FINANCE |
210 | vvDiscountName | Discount Name | deferredSelect | FINANCE |
220 | vvDiscountPercentage | Discount Percentage | deferredSelect | FINANCE |
230 | vvDiscountAmount | Discount Amount | InputType.textField | FINANCE |
240 | vvTotalScheduledQty | Total Scheduled Qty | InputType.textField | DEFAULT |
250 | sdSoLineId | Sd So Line Id | InputType.number | REFERENCE |
260 | srcEntityName | Src Entity Name | deferredSelect | DEFAULT |
270 | srcEntityId | Src Entity Id | InputType.textField | REFERENCE |
280 | sdSoHeaderId | Sd So Header Id | InputType.number | REFERENCE |
290 | lineNumber | Line Number | InputType.number | DATA |
300 | shippingOrgId | Shipping Org Id | deferredSelect | REFERENCE |
310 | invItemMasterId | Inv Item Master Id | deferredSelect | REFERENCE |
320 | itemDescription | Item Description | deferredSelect | DEFAULT |
330 | lineQuantity | Line Quantity | InputType.textField | DATA |
340 | priceListHeaderId | Price List Header Id | InputType.number | REFERENCE |
350 | priceDate | Price Date | InputType.date | DATE |
360 | unitPrice | Unit Price | InputType.textField | FINANCE |
370 | linePrice | Line Price | InputType.textField | FINANCE |
380 | taxAmount | Tax Amount | InputType.textField | FINANCE |
390 | taxCode | Tax Code | deferredSelect | FINANCE |
400 | docStatus | Doc Status | InputType.select | CONTROL |
410 | docStatus | Doc Status | InputType.select | CONTROL |
420 | needByDate | Need By Date | InputType.dateTime | DATE |
430 | promiseDate | Promise Date | InputType.date | DATE |
440 | scheduleShipDate | Schedule Ship Date | InputType.date | DATE |
450 | referenceDocType | Reference Doc Type | InputType.textField | CONTROL |
460 | referenceDocNumber | Reference Doc Number | InputType.number | DATA |
470 | soDocumentTypeLine | So Document Type Line | deferredSelect | CONTROL |
480 | supplySource | Supply Source | InputType.select | DEFAULT |
490 | destinationType | Destination Type | InputType.select | CONTROL |
500 | lineDescription | Line Description | InputType.textField | DEFAULT |
510 | uomCode | Uom Code | deferredSelect | DEFAULT |
520 | kitCb | Kit Cb | InputType.switchField | DEFAULT |
530 | kitConfiguredCb | Kit Configured Cb | InputType.switchField | DEFAULT |
540 | approvalStatus | Approval Status | InputType.select | CONTROL |
550 | sysSpdHeaderId | Sys Spd Header Id | InputType.number | REFERENCE |
560 | discountCode | Discount Code | deferredSelect | FINANCE |
570 | lineDiscountAmount | Line Discount Amount | InputType.textField | FINANCE |
620 | shipToId | Ship To Id | deferredSelect | REFERENCE |
630 | billToId | Bill To Id | deferredSelect | PLANNING |
640 | lineType | Line Type | InputType.select | CONTROL |
5580 | createdBy | Created By | InputType.textField | REFERENCE |
5590 | creationDate | Creation Date | InputType.dateTime | REFERENCE |
5600 | lastUpdatedBy | Last Updated By | InputType.textField | REFERENCE |
5610 | lastUpdateDate | Last Update Date | InputType.dateTime | REFERENCE |
Details
The system creates multiple details for each line depending upon the line type (ITEM, FREIGHT, TAX, etc.). Though you don't need to regularly review/update transaction detail lines, It's advisable to review accounts and amounts after setup changes.
Depending upon your configuration, the details of a line are shown either on a separate tab or in the links section of lines.
Click on the Details button below a line to view/update/create details. By default, when saving any line system adds detail with the quantity, price, and account details. You can add multiple details and change the account/quantity as per your actual requirement.
Click on the expandable button to view the fields of a detail line.
To create a new detail, click on Add New Line button. You can also copy an existing detail line to a new one by clicking on the Copy Line button.
In the data section, enter the detail line number. The system always creates the first line as line number 1, but you can change it. While adding a new detail line, enter a detail line number as its mandatory field. Enter the detail quantity in the quantity field.
The reference groups show various ids for reference only. You don't need to enter any information in this section.
All Fields
Name | Sequence | Label | InputType | Field Group |
---|---|---|---|---|
10 | vvOrgCode | Org Code | deferredSelect | ENTITY |
10 | vvItemNumber | Item Number | deferredSelect | DEFAULT |
20 | vvUomCode | Uom Code | deferredSelect | DEFAULT |
30 | vvUomDescription | Uom Description | deferredSelect | DEFAULT |
40 | vvItemStatus | Item Status | deferredSelect | CONTROL |
50 | vvSdSoHeaderId | Sd So Header Id | InputType.number | REFERENCE |
60 | vvLineNumber | Line Number | InputType.number | DATA |
70 | vvShippingOrgId | Shipping Org Id | deferredSelect | REFERENCE |
80 | vvInvItemMasterId | Inv Item Master Id | deferredSelect | REFERENCE |
90 | vvItemDescription | Item Description | deferredSelect | DEFAULT |
100 | vvLineQuantity | Line Quantity | InputType.textField | DATA |
110 | vvTotalScheduledQty | Total Scheduled Qty | InputType.textField | DEFAULT |
120 | vvDetailLocator | Detail Locator | deferredSelect | ENTITY |
130 | sdSoDetailId | Sd So Detail Id | InputType.number | REFERENCE |
140 | srcEntityName | Src Entity Name | deferredSelect | DEFAULT |
150 | srcEntityId | Src Entity Id | InputType.textField | REFERENCE |
160 | sdSoLineId | Sd So Line Id | InputType.number | REFERENCE |
170 | shipmentNumber | Shipment Number | InputType.number | DATA |
180 | subInventory | Sub Inventory | deferredSelect | ENTITY |
190 | locatorId | Locator Id | deferredSelect | REFERENCE |
200 | requestor | Requestor | InputType.textField | DEFAULT |
210 | shipToLocationId | Ship To Location Id | InputType.number | REFERENCE |
220 | uomCode | Uom Code | deferredSelect | DEFAULT |
230 | quantity | Quantity | InputType.textField | DATA |
240 | needByDate | Need By Date | InputType.dateTime | DATE |
250 | promiseDate | Promise Date | InputType.date | DATE |
260 | scheduleShipDate | Schedule Ship Date | InputType.date | DATE |
270 | status | Status | InputType.textField | CONTROL |
5280 | createdBy | Created By | InputType.textField | REFERENCE |
5290 | creationDate | Creation Date | InputType.dateTime | REFERENCE |
5300 | lastUpdatedBy | Last Updated By | InputType.textField | REFERENCE |
5310 | lastUpdateDate | Last Update Date | InputType.dateTime | REFERENCE |
Actions
Actions allow you to change the status of the transaction. The system creates transactions in draft status. When you are ready to publish the transaction and send it to the customer, change it to Confirmed. You can cancel a transaction by clicking on the Cancel button. Similarly, you can close any transaction by clicking on the Close button.
A confirmed transaction can be converted to other documents, and the corresponding buttons are available in the actions section.
Accounting
The accounting process in inoERP is quite flexible, and you can configure the system to generate the accounting details for any business process.(Refer to Journals for more details)
If you enter any accounting profile on the transaction header, the system will use the accounting profile to derive the accounts. Else, the system will use the default accounting profile for the business unit.
You can default accounting profile from 3 levels
- Transaction
- Billing Document Type
- Business Unit
Invoice
DR Receivables
CR Revenue
CR Tax
CR Freight
Credit Memo
DR Revenue
DR Tax
DR Freight
CR Receivables
Debit Memo
DR Receivables
CR Revenue
CR Tax
CR Freight
Line Categories
In AR, the system will allow you to use separate accounts for below line categories:
- item
- freight
- service
- misc
- tax
- misc
- misc3
So, if an invoice has any line with any of the above line categories, the system will use the corresponding accounts.
Example:
Line 1 : Inventory Item
Line 2 : Service Item
Line 3 : Misc. Item
Accounting Entries For Line 1
DR Receivables
CR Revenue For Inventory Item
CR Tax
Accounting Entries For Line 2
DR Receivables
CR Revenue For Service Item
CR Tax
Accounting Entries For Line
DR Receivables
CR Revenue For Misc. Item
CR Tax
Draft Accounting
You can view the details of the draft accounting entries in the draft accounting tab. Draft accounts are generated when you click on the "Create Draft Accounting" button. The draft accounting entries always delete the existing entries. You can also manually delete the draft accounting entries by clicking on the "Delete Draft Accounting" button.
The system allows you to update the draft accounting entries. You can edit the debit and credit amounts and also the accounts. To create journal entries with your updated values, use the "confirm draft accounting" button.
You can use the "create accounting entries" button to create journal entries with the original values.
Combination
The GL account code combination is a mandatory field. You can rename the field as per the term of your existing accounting system.
The system derives the GL account code from the selected accounting profile. If you change the accounting combination, the system will default all the other related fields from the chosen combination.
Period Name
A read-only field. It displays the period name for the selected period—the value defaults from the Draft Journal Header.
Amount
The amount is a mandatory field. You can enter the amount in the currency of the selected business unit.
D or C
The D or C field is a mandatory field. You can select either Debit or Credit.
Final Accounting
You can view the details of the final accounting entries in the final accounting tab. Final accounts are generated when you click on the "Create Accounting" button. The final accounting entries can't be deleted and can only be updated on the Journal screen (Updates are only allowed before posting).
Combination
The GL account code combination is a mandatory field. You can rename the field as per the term of your existing accounting system.
The system derives the GL account code from the selected accounting profile. If you change the accounting combination, the system will default all the other related fields from the chosen combination.
Period Name
A read-only field. It displays the period name for the selected period—the value defaults from the Journal Header.
Amount
The amount is a mandatory field. You can enter the amount in the currency of the selected business unit.
D or C
The D or C field is a mandatory field. You can select either Debit or Credit.
Credit Memo
The process of creating a credit memo is the same as creating an invoice. Follow the steps mentioned in Header, Line & Detail section to create a credit memo. Select the document type as "Credit Memo."
You can also convert an invoice to a credit memo using the "Convert to credit" action.
Debit Memo
The process of creating a debit memo is the same as creating an invoice. Follow the steps mentioned in Header, Line & Detail section to create a debit memo. Select the document type as "Debit Memo."