Suppliers Setup (SUS) is used to enter and maintain all of the information relating to an organization from which you purchase goods or services.

Click here to see the screenshot
A supplier is linked to a creditor/payables account in the Financials ledger. This account holds all of the financial postings for the supplier. When you add a new supplier you can create the associated creditor/payables account at the same time by entering all of the chart of accounts details. Alternatively, if you have already created the account, you can reference this chart of accounts code to display the ledger account details.
Note: It is important that this link between the supplier and the Financials creditor/payables account is established.
A large amount of information can be held for a supplier and these details are often divided into a series of logical tabs on the form (depending on the form design). Some of the details are only required if you are using the appropriate SunSystems facility for example, the Order Entry details are only required if you are using SunSystems Order Fulfilment.

Discuss in forum
Payment Terms Setup (PYTRMS) is used to define the payment terms details in two parts: first a payment header is defined to identify the terms, then one or more payment term details are defined.

Each payment term detail contains the calculation requirements for a single type of date, for example due date, or discount date 1.

If a set of payment terms changes, you should alter the terms using Payment Terms Setup (PYTRMS). The revised terms apply immediately to any new transactions entered using the terms code.
Note: You can use Payment Terms Update (PTU) to apply a new payment term to a selection of existing transactions to which terms have not previously been applied.

Payment Profiles Setup (PPS) is used to define the criteria by which transactions are selected for payment in Payment Run (PAY), or for collection in Payment Collection Run (PAYC).

Discuss in forum
If your requirements are very straightforward, you may only require a single payment profile for your payment runs, and another single profile for your payment collection runs. These profiles might simply select all transactions due up to a selected date, for all your creditor/payables, debtor/receivables and client accounts.

However, in practice, you will probably develop several different payment profiles that select transactions using more complex selection criteria. There are a large number of parameters and selection criteria available on a payment profile to allow you to select exactly the accounts and transactions you want to pay. This enables you to manage and maximize your cash flow.

For example, you might create a profile that includes a number of currencies, all of which are paid from, or into, the same bank or bank account. Another example might be to create a set of profiles that selects transactions according to the account priority to select high, medium or low priority suppliers or customers in different payment runs.

Another advantage of defining various payment profiles is that when Payment Run or Payment Collection Run is used for a particular profile, the resulting payments file acquires a code which is unique to the profile. See What is the Payment File?

When you define a payment profile you can pick up to five selection criteria to be used as run time criteria. For example, you may want to enter the range of accounts to be considered for payment at run time, rather than setting a predefined range in the profiles.

Payment profiles are defined using Payment Profiles Setup. The same form is used to define the profiles for a Payment Run and a Payment Collection Run. However, one of the profile options identifies whether the profile is to be used for a payment run or a payment collection run.

Tip: You can reference a payment profile on a journal type, if you always want to pay the transactions for this journal type immediately after the journal is posted.