Sovos Wiki
-
GST Compliance Solution
-
- GSTR 9 Structural and Business Rules
- ITC 04 Structural and Business Rules
- GSTR 8 Structural and Business Rules
- GSTR 7 Structural and Business Rules
- GSTR 6 Structural and Business Rules
- GSTR 3B Structural and Business Rules
- GSTR 2 Structural and Business Rules
- GSTR 1 Structural and Business Rules
- Validation Rules of Sovos GST Compliance Solution
-
- GSTR 1 and GSTR 1A
- Introduction to GSTR-1 and GSTR-1A
- GSTR-1: Process Flow
- GSTR-1: Upload Sales Register
- GSTR-1: View and Change Uploaded Data
- GSTR-1: Get E-Invoice Data
- GSTR-1: Perform E-Invoice Reconciliation
- GSTR-1: Create the Draft and Review the Summary
- GSTR-1: Save Data to the GST Portal
- GSTR-1: File the Return
- GSTR-1 Bulk Mode: Introduction and Process
- GSTR-1 Bulk Mode: Get & Upload and View
- GSTR-1 Bulk Mode: Create, Save and File
- GSTR-1A: Introduction and Process
- GSTR-1A: Upload and View
- GSTR-1A: Create, Save and Summaries
- GSTR-1A: File the Return
- GSTR-1 and GSTR-1A: Troubleshooting
- Show Remaining Articles (3) Collapse Articles
-
- Introduction to IMS Reconciliation
- IMS: Process Flow
- IMS: Prepare Your Data and Get IMS Data
- IMS: Perform Reconciliation
- IMS: Advanced Reconciliation Rules
- IMS: Reconciliation Categories
- IMS: Review Results in IMS Recon Result
- IMS: Take Action on Invoices
- IMS: Act on Reconciled Invoices with a File
- GET & Action IMS: Action Data
- IMS: Resolve Mismatches
- IMS: Save to GSTN and Regenerate GSTR-2B
- IMS: Send Single and Bulk Mail to Vendors
- IMS: Filters and Downloads
- IMS: Troubleshooting
-
- Introduction to GSTR 2A Reconciliation
- GSTR 2A: Process Flow
- GSTR 2A: Prepare Your Data and Get GSTR-2A
- GSTR 2A: Perform Reconciliation
- GSTR 2A: Advanced Reconciliation Rules
- GSTR 2A: Reconciliation Categories
- GSTR 2A: Review Results in B2B and CDN Recon Result
- GSTR 2A: Snapshot
- GSTR 2A: Summary
- GSTR 2A: Category-wise Vendor Summary
- GSTR 2A: Net Vendor Summary
- GSTR 2A: Post Action Summary
- GSTR 2A: 2B Missing Invoices
- GSTR 2A: Take Action on Invoices
- GSTR 2A: Reconcile Invoices Manually
- GSTR 2A: Delink and Delete 2P
- GSTR 2A: Download and Update GSTR-2B Details in Recon
- GSTR 2A: Mark ITC for GSTR-3B
- GSTR 2A: Send Single and Bulk Mail to Vendors
- GSTR 2A: Download Results
- GSTR 2A: Monthly Recon Result (2P Base)
- GSTR 2A: Know Your Monthly ITC
- GSTR 2A: Group (PAN) Level Reports
- GSTR 2A: GSTIN Level Reports
- GSTR 2A: Recon Tracker
- GSTR 2A: Bulk Download of Data and Results
- GSTR 2A: Troubleshooting
- Show Remaining Articles (12) Collapse Articles
-
- Introduction to GSTR 2B Reconciliation
- GSTR 2B: Process Flow
- GSTR 2B: Prepare Your Data and Download GSTR-2B
- GSTR 2B: Perform Reconciliation
- GSTR 2B: Advanced Reconciliation Rules
- GSTR 2B: Reconciliation Categories
- GSTR 2B: Review Results in B2B and CDN Recon Result
- GSTR 2B: Snapshot
- GSTR 2B: Summary
- GSTR 2B: Category-wise Vendor Summary
- GSTR 2B: Net Vendor Summary
- GSTR 2B: Group (PAN) Level Reports
- GSTR 2B: GSTIN Level Reports
- GSTR 2B: Dashboard
- GSTR 2B: Take Action on Invoices
- GSTR 2B: Reconcile Invoices Manually
- GSTR 2B: Delink and Delete 2P
- GSTR 2B: Mark ITC for GSTR-3B
- GSTR 2B: Send Single and Bulk Mail to Vendors
- GSTR 2B: Download Results
- GSTR 2B: Troubleshooting
- Show Remaining Articles (6) Collapse Articles
-
- Introduction to 2P Purchase Register Upload
- 2P: Upload Methods
- 2P: Process Flow
- 2P: Records Not Considered for Reconciliation
- 2P: Document Types and Invoice Types
- 2P: Input Format Files
- 2P: GSTR2 (1) Fields, Regular Transactions and CDN
- 2P: GSTR2 (1a) Fields, Composition, Unregistered and Nil (Aggregate)
- 2P: GSTR2 (2) Fields, ISD Invoice
- 2P: GSTR2 (4) Fields, ITC Reversal and Reclaim
- 2P: GSTR2 (5) Fields, HSN Summary
- 2P: Key Rules and Constraints
- 2P: Structural Errors
- 2P: Business Errors and Warnings
- 2P: Abbreviations
-
E-invoicing Solution
-
E-way Bill Solution
-
Taxpayer APIs
-
Garnet
Create and Edit rules
Create and Edit Rules
For transforming your customized ERP output into Sovos Input format, you need to prepare the rule file. In short, the rule means mapping ERP column headers with column header available in Sovos Input format.
The rule file will be an XML file. The return type and section type selected by you on this create rule page will get stored in the rule file and accordingly, data will get converted.
Process for creating rules are as follows:
1. Click on Create rule File option and select Create and Edit Rules.
2. Firstly browse your ERP output
3. Sheet number – A file may contain single or various sheets. The number of the sheet whose data needs to be converted needs to be entered in this option. E.g. if in sheet 1 ERP data is present then here value need to enter as “1”
4. Row No of Header of ERP Output – Here you need to mention row no. in which your data’s headers are mentioned. E.g. Headers are present in row 3 then here you need to provide value as “3”
5. Rule File – For first time user no need to browse rule File. If rule file is already created then you need to browse that file.
6. Return Type – Here you need to select return type from the drop-down whether this data is related to GSTR 1, GSTR 2 and GSTR 6 and counterparty master.
7. Section – Select return section from drop down. E.g. For GSTR 1 return, a section should be selected based on ERP data like Regular transactions / B2CS aggregate/ Advances and Tax Paid, etc.
8. Now click on “Add Rule”
- Here you need to map your ERP output column with Sovos Input format column e.g. for invoice number heading provided in ERP out is “Document Number” and in Sovos Input format it is “Invoice/Document number” then here you need to select these headings accordingly as shown in the above screenshot
- Then select Master rule from the drop-down. So that rule expression will get created. Master’s rules expressions are available as follows Column Mapping: This will map a column of your data with our respective platform format. Once you select a column from your data and our respective platform format and select column mapping the two columns will be mapped and a rule will get created. Conditional Mapping: This will be if-else rule. Here you can derive values of a particular column of our respective platform format using one or more than one column of your data. Default column numbers of this rule will be s1, s2. You need to replace default column numbers with the one present in your data. To help you to replace the column numbers the details of columns used are given below the rule in description Terminology Mapping: This will be switch-case rule and it will be applicable in those cases wherein you are using some different code and we are using our own short forms. In this case, you can select only one column from your data which he can map with a column of our respective platform format. Once this rule gets selected you need to replace the word <code> with his internal code. If you don’t want to chose any above-mentioned master rule then select None from drop down and enter your own rule expression in Enter Rule. For reference, you can see more rule expression in the “References” tab
- Column Mapping: This will map a column of your data with our respective platform format. Once you select a column from your data and our respective platform format and select column mapping the two columns will be mapped and a rule will get created.
- Conditional Mapping: This will be if-else rule. Here you can derive values of a particular column of our respective platform format using one or more than one column of your data. Default column numbers of this rule will be s1, s2. You need to replace default column numbers with the one present in your data. To help you to replace the column numbers the details of columns used are given below the rule in description
- Terminology Mapping: This will be switch-case rule and it will be applicable in those cases wherein you are using some different code and we are using our own short forms. In this case, you can select only one column from your data which he can map with a column of our respective platform format. Once this rule gets selected you need to replace the word <code> with his internal code.
- If you don’t want to chose any above-mentioned master rule then select None from drop down and enter your own rule expression in Enter Rule. For reference, you can see more rule expression in the “References” tab
9. Once rule entered click on Save Rule. Also before saving rule, if you want to check whether a rule is working properly or not, so for this click on check rule and enter your source value and click on Validate. If the rule is working properly target value will come as expected. If the result is not as expected then it means there is some issue in rule and needs to work on rule again. So once rule created now click on Save rule. Likewise, add rules for all columns.
10. Once add rule is done, click on “Generate Rule File” and provide a name with .xml extension and provide a path where to save that XML rule file. Kindly note here, after adding rules it is important to generate rule file, don’t directly move to another tab because you may lose all rules added by you.
11. Also, the option of edit rule is available. You just need to select the rule which you want to edit and click on edit rule.
So window same of that rule will get opened and then you can make a change in a rule as required and then save the rule.
12. Similarly, the delete rule option is available. You just need to select the rule and click on delete for deletion of the specific selected rule.
Once the rule file generated, now for data transformation go to Transformation and Validation Data.