Explanation
D: When you void a payment, Payables automatically reverses the accounting and payment records so your general ledger will have the correct information, and so the status of the paid invoices is reset to Unpaid. Payables also reverses any realized gains or losses on foreign currency invoices recorded as paid by the payment.
B: If you withhold taxes at payment time and you void a payment that paid an invoice with an associated withholding tax invoice, then Payables automatically creates a negative (reversing) invoice for the tax authority supplier to offset the amount of the tax withholding invoice. You determine when you withhold taxes by selecting the Apply Withholding Tax option in the Payables Options page.
References: Oracle Payables User's Guide, Voiding Payments Using the Payments Window

Explanation
Reference Data Sets
You begin this part of your implementation by creating and assigning reference data to sets. Make changes carefully as changes to a particular set affect all business units or application components using that set. You can assign a separate set to each business unit for the typeofobject that is being shared. For example, assign separate sets for payment terms, transaction types, and sales methods to your business units.
Your enterprise can determine that certain aspects of your corporate policy can affect all business units. The remaining aspects are at the discretion of the business unit manager to implement. This allows your enterprise to balance autonomy and control for each business unit. For example, your enterprise holds business unit managers accountable for their profitand loss, but manages working capital requirements at a corporate level.
In such a case, you can let managers define their own sales methods, but define payment terms centrally. In this example:
Each business unit has its own reference data set for salesmethods.
One central reference data set for payment terms is assigned to all business units.
References:https://docs.oracle.com/cloud/latest/financialscs_gs/FAIGL/FAIGL1493157.htm#FAIGL94314

Explanation
Accounts payable specialists can view the list of scanned images for invoice entry, along with the additional routing attributes, in the Scanned Invoices region of the Invoices work area.
References:http://docs.oracle.com/cd/E36909_01/fusionapps.1111/e20375/F569958AN60E65.htm

Explanation
When you apply a prepayment to an invoice, the tax rate at the time of prepayment may differ from the tax rate at the time that the prepayment is applied to an invoice. Oracle Fusion Tax considers the tax calculated on the prepayment according to the value assigned to the Applied Amount Handling option in the tax record. The values are Recalculated and Prorated.
For example, you apply a prepayment amount of 5,000 USD to an invoice with a total amount of10,000 USD.
At the time of prepayment, the applicable tax rate was 5% (250 USD tax on the prepayment); at the time of invoice creation, the applicable tax rate is 10%. Tax is calculated in this way:
* Recalculated: The tax is recalculated on the prepayment using the invoice tax rate and the same tax rate is applied to the invoice line amount. The tax calculation creates two tax lines: one for the invoice line amount and one for the prepayment with a negative amount. In the invoice example, the calculationcreates an invoice line amount tax line of 1,000 USD (10% * 10,000 USD) and a prepayment tax line of -500 USD (10% * -5000 USD). This reverses tax calculated on the invoice for the prepayment amount applied. The tax calculated on the prepayment is retained.
* Prorated:Etc.
References:https://docs.oracle.com/cloud/farel8/financialscs_gs/FAFTT/F1006655AN242EE.htm