Tasks to be completed when documenting an operation (from creation to publication)

 1. Enter the Title of the operation / page

2. Add the following Labels : 

    • Scope of applicability: ww, country_accounting 

    • Country or group of countries (if applicable): belux, china, france, italy, lam, nam, uk_ie, bulgaria, dach, netherlands, iberia, poland, latvia, australia, india, japan, south_korea, thailand, singapore, new_zealand, emea_transversal, apac_transversal

    • Unit and Domain according to the List of labels to be used in the Finance Service Line space

      • E.g. 1: WW Operation in Financial Accounting under domain "Central Finance Processes & Compliance":
        • Labels to be used: ww, financial_accounting, central_fin_proc_compliance

      • E.g. 2: France Operation in Financial Accounting:
        • Labels to be used: country_accounting, france, financial_accounting
          (for country operations, the Domain is always country_accounting)


3. Fill in all fields as described above

4. Name the title of each section using OPD methodology naming convention - Infinitive verb without the “to”, mainly action verb...something) - " I do something..."

5. Once the description of the operation is completed, ensure it is approved and published by launching the SBS-Finance approval workflow 


Domain: Treasury Backoffice APAC

Responsibility area: Respect of Treasury Policy Rules

Table of contents 

By default the table of contents displays Heading 1 & Heading 2 (other levels can be added)


Scope

3. Remove the icon when not applicable


ERP

4. Remove the icon(s) when not applicable


Frequency

5. Remove the icon(s) when not applicable

 

References

6. Add the link to SAP transaction(s) (when it exists)



Forms

7. Insert the links accordingly and change the link text with the Form name



Attachments

8. Add the link to attachments or external links




Previous operation << >> Next operation



1. Objective and Scope

1.1. Objective of this Operation

WHY - Describe the objective of the operation


1.2. Scope

Detail the scope (legal entities, etc.)


2. Definitions

Definitions should be added in the Finance Glossary - Add definition and link it to respective Letter in Finance Glossary 

See Finance Glossary:

  • ...


3. Tasks description

WHAT and HOW - Main content of the operation

The content should be mainly organized in 2 levels of Headings to ensure a proper link with the Table of Contents.

Select the level of heading in the "Paragraph" option.

3.1. I reconcile the FX Deals with External Banks in Quantum to ensure the deals entered by Corporate Treasury Team are matched with bank records timely. The confirmation can be either via electronic or manual confirmation.

3.1.1. Deal created

3.1.1.1 Electronic trade in 360T / Bloomberg

I receive an email from Corporate TR team for the deal done in trading tools.


3.1.1.2 Manual Create deal

I receive an email from Corp TR team for manually created deal

3.1.2. I check in Quantum whether the deal interfaces from the trading platform correctly.

In this example, the deal was interfaced correctly. Under the 'Message Status' when not yet confirmed with the bank will show 'Unmatched'.


3.1.3. Deal confirmation

3.1.3.1 Electronic Confirmation (Misys)

If the company implements the electronic confirmation (Misys) and no technical issue between Misys and Quantum, the message status will show as 'Electronically matched' roughly 5-10 mins after the deal is created.

3.1.3.2 Manual Confirmation (Paper, email, etc)

If the company doesn't implement the Misys (or such service is not available at the bank, we'll need to confirm the deal with the bank and log on to Quantum to update the status as 'Manually Matched'.

To manually match (confirm the correctness of the deal) in Quantum, click on the Message Status 

Click 'Match now'

The status will be changed to 'Manually Matched'


Some bank may require you to send the paper confirmation where you'll need to process in addition to this manual confirmation in Quantum.

End of document.