Data/Information Submission Guide

Created by Jordan Axel Bilyard, Modified on Tue, 16 Sep at 2:30 PM by Jordan Axel Bilyard

PDF Document Downloadable here.


Welcome to Trade Shield! This guide provides the essential information needed to prepare and submit the data required for the setup of your Credit Management Module.


Information Needed for Limit Review Workflow

To configure your credit limit review workflow, we will require the following assets:

  • Company Logo
  • Link to your company's privacy policy
  • Approval Process (Speak to your Customer Success Manager for a workflow approval process template)

Aging and Customer Masterfile Data Information Needed

  1. Aging and Masterfile data can be shared as one file, or two separate files, as long as each file contains the customer account number for matching.
  2. The data should include the below information. Fields marked with * are mandatory:
  • Customer Account Number *
  • Customer Name *
  • Payment Terms *
  • Payment Term Description
  • Credit Limit *
  • Customer Registration Numbers/VAT Numbers (Both if available) or ID Numbers (For sole proprietors) *
  • Aging Buckets * (e.g. current, 30, 60, 90, etc)
  • Currency (Mandatory if there are values in your aging other than ZAR)
  • Business Unit/Division
  • Branch/Region
  • Account Personnel
  • Credit Personnel
  • Sales Personnel

How to Submit Files:

This information can be submitted directly to filesubmissions@tradeshield.ai with your Customer Success Manager in copy. Alternatively, you can submit this information via SFTP. Please contact your Customer Success Manager to obtain your account-specific SFTP details.

File Naming Convention:

Each data submission should be labelled with the date of the file as Year-Month-Day (YYYY-MM-DD) followed by your organization's business name. For example: 2025-09-16-YourBusinessName.xlsx

Initial Submission of 12-Month Historic Aging

  1. Please share more than 12 months of historic data if it is available.
  2. Your initial submission should include the latest 12 months of historic month-end aging. Each month-end report can be a separate file or included as a separate tab in the same spreadsheet.
  3. If you are conducting a Proof of Concept (POC) with Trade Shield, please submit this information with your Sales Executive in copy.

Ongoing Submission of Aging and Master File

  1. Ongoing data can be submitted directly to filesubmissions@tradeshield.ai with your Customer Success Manager in copy, or via your designated SFTP folder.
  2. Data can be submitted on a monthly, weekly, or daily frequency. We recommend sharing data as frequently as possible (weekly or daily). If you have customers with 7-day payment terms, we recommend a minimum frequency of weekly submissions.
  3. A month-end file must be submitted each month. This is the minimum requirement for Trade Shield to successfully host and update your platform.

FAQs: Data Submission

Why do we require Masterfile information?

The Masterfile data acts as the foundation for setting up your Trade Shield platform. It contains identifying information about each customer, ensuring accuracy in matching accounts to the relevant legal entity in our database. It also provides details on payment terms, credit limits, and other attributes that allow us to create filters, helping you view your debtors book in segments.

Why do we require frequent aging data?

Aging data allows us to capture a customer's credit usage and repayment behaviour over time. These details are essential for monitoring credit health, identifying risk, and enabling proactive management. Frequent aging submissions (daily/weekly) allow your team to have an up-to-date view of their customers' aging in Trade Shield, which helps us predict trends and identify customers who may pose a risk for future late payment or default.

Was this article helpful?

That’s Great!

Thank you for your feedback

Sorry! We couldn't be helpful

Thank you for your feedback

Let us know how can we improve this article!

Select at least one of the reasons
CAPTCHA verification is required.

Feedback sent

We appreciate your effort and will try to fix the article