July 1, 2008
There are two major categories of interfund/interagency activities: reciprocal and nonreciprocal.
Reciprocal interfund/interagency activity is the internal counterpart to exchange and exchange-like transactions. It includes interfund loans (refer to Subsection 85.90.20), and interfund services provided and used (refer to Subsection 85.90.30).
For information on paying interfund/interagency billings, refer to Subsection 85.36.20.
July 1, 2001
Interfund loans are reciprocal in nature. They are amounts provided with a requirement for repayment within a reasonable time. Interfund loans are reported as interfund receivables ("due from") in lending funds and interfund payables ("due to") in borrowing funds. Loans due within one year should be classified as short-term and loans due beyond a year should be classified as long-term. Refer to Subsection 85.54.30.
January 1, 2012
|Interfund/interagency services provided and used|
Interfund/interagency services provided and used are also reciprocal in nature. They were previously termed "quasi-external transactions." Interfund/interagency services provided and used are transactions within the state that are similar to and reported as though they had occurred with organizations external to the state. Interfund/interagency services provided and used are to be accounted for consistently by the accounts involved.
At the end of each fiscal period, any unpaid or unsettled amounts are reported as either interagency or interfund receivables and payables. Refer to Subsection 85.95.40 for illustrative entries.
To record interfund/interagency services provided and used, the paying agency records an expenditure/expense using an appropriate object of expenditure. The receiving agency records revenue using either Revenue Source Code 0420 "Charges for Services," 0450 "Sales of Goods and Supplies - Proprietary Funds," or another appropriate revenue source code. Interfund/interagency services provided and used are budgeted and accounted for in this manner.
The following are examples of interfund/interagency services provided and used:
June 1, 2016
|Payment procedures for selected central services agency charges|
The following are selected central services agencies which require the use of unique object codes by the paying agency. A listing of services provided is as follows:
The following object codes and payment schedules are to be used by the paying agency for transactions with selected central services agencies:
Unless otherwise provided above, central service agencies are to present invoices for payment to receiving agencies within 15 calendar days after the end of each billing period. However, at fiscal year-end, all bills (actual and estimates) are to be invoiced per the current fiscal year closing calendar in Subsection 90.20.05.
When problems arise with the collection of interagency receivables, the following steps are to be taken:
July 1, 2008
Transfers are nonreciprocal in nature. Transfers of equity, formerly known as residual equity transfers, are non-recurring, non-routine transfers of equity between accounts. Two examples of equity transfers are contributions to or return of contributions from proprietary fund type accounts and transfer of residual equity balances from discontinued accounts.
Transfers of equity are generally infrequent. The key to identifying equity transfers is their non-recurring or non-routine nature. If transactions are recurring or routine, particularly if they involve a subsidy relationship, they are reported as operating transfers. Refer to Subsection 85.90.50.b
Equity transfers are recorded in governmental fund type accounts using Revenue Source Codes 0678 "Equity Transfers In" or 0679 "Equity Transfers Out." Equity transfers in proprietary fund type accounts are recorded to Revenue Source Code 0820 "Capital Contributions." Refer to Subsection 85.95.20 for illustrative entries.
All equity transfers are to be in balance at the agency level, except for the following:
Operating transfers include the following:
Operating transfers are recorded as expenditures using Object M or as revenues using the 06XX revenue source codes. Refer to Section 75.80 for a listing and description of all transfer revenue source codes. Refer to Subsection 85.95.30 for illustrative entries.
Operating transfers net to zero at the agency level.
Special budgeted allocations generally give agencies additional spending authority, but no additional cash is provided for federal, private/local or dedicated operating accounts. Two examples of these budgeted, noncash allocations are the Salary and Insurance Contribution Increase Allocation and the Special Retirement Contribution Increase Allocation. An expenditure transfer is required for the General Fund - State account allocation. Two transfer transactions - one for the expenditure transfer and one for the revenue transfer - out of the operating account and into the allocation account are required for the federal, private/local and dedicated operating account allocations. Refer to Subsection 85.95.35 for an illustrative entry.
In governmental fund type accounts, transfers are reported as other financing uses in the funds making the transfers and as other financing sources in the funds receiving the transfers. In proprietary funds, transfers are reported in a separate section below nonoperating revenues and expenses.
In instances where transfers are appropriated as expenditures, GAAP and budgetary accounting treatments will differ. For budgetary reporting, appropriated operating transfers are considered "expenditures," while for GAAP reporting purposes, as noted above, they are considered other financing uses.
July 1, 2009
|Reimbursements (Objects S & T)|
Reimbursements are recorded when one agency and/or account initially charges an expenditure/expense that is subsequently charged to another. Generally, the reimbursement is recorded as an expenditure/expense in the reimbursing account and as a reduction of a corresponding expenditure/expense in the reimbursed account. Accounting for reimbursements in this manner results in the expenditure/expense being reported only once and in the proper account. Reimbursements are to be appropriately documented and approved.
Reimbursement reporting is to be used only in circumstances as described above. It is not to be used for interfund loans, interfund transfers, or other interfund activities. Additionally, payments received by proprietary funds for goods and services are normally recorded as revenue with appropriate revenue source codes rather than as reimbursements.
As described below, reimbursements are coded with Object S or Object T. The subobject coding should reflect the object of expenditure being offset with the reimbursement, except Subobject JA “Noncapitalized Assets” and Subobject JB “Noncapitalized Software” which are coded to Subobjects SE and TE. Although Subobjects SZ and TZ “Unidentified” are available for use, it is preferable that an agency allocates charges to the appropriate subobject of expenditure within Objects S and T on a monthly basis.
Reimbursements are classified into two types:
Intra-agency reimbursements (Object T) - Intra-agency reimbursements are used to charge for services or supplies provided by one account to another and to distribute administrative overhead charges. In accounting for intra-agency reimbursement transactions, the reimbursed account other than a non-budgeted proprietary type account is to credit expenditures using object T. The reimbursing account is to account for intra-agency materials supplied or services rendered as object T and the appropriate sub-object.
Intra-agency reimbursements are to be used to record special budgeted allocations involving accounts 239 "Tort Defense Service Revolving Account," 406 "Salary and Insurance Increase Revolving Account," 426 "Digital Government Revolving Account," and 427 "Special Account Retirement Contribution Increase Revolving Account." Refer to Subsection 85.90.50.c.
Agencies may request a waiver from complying with specific requirements of this section. The request is to be in writing and be approved in writing by OFM before the waiver takes effect. Waivers automatically expire at the end of the fiscal biennium for which they were granted and are to be re-approved in writing to remain in force.
Accounts other than non-budgeted proprietary fund type accounts
All accounts other than non-budgeted proprietary fund type accounts are to use Object T transfers to record intra-agency transfers between said accounts. Reimbursements to accounts for expenditures/expenses initially made from it which are properly applicable to another account are to be recorded as a credit to expenditures/expenses using Object T. The reimbursing account other than a non-budgeted proprietary fund type account is to debit expenditures/expenses using Object T.
When transfers of salaries are made with Subobject TA, the FTEs are to remain with the original Object A expenditure.
The total for Object T transfers at the subobject level is to equal zero for all accounts within a fiscal year except as noted below for GL Code 6525 transfers and for non-budgeted proprietary fund type accounts. Refer to Subsection 85.95.50.a and b for illustrative entries.
Intra-agency reimbursements received by budgeted proprietary fund type accounts are recorded as credits to expense using Object T. Therefore, an additional entry is necessary to adjust to proper GAAP accounting. The GAAP adjustment debits GL Code 6525 “Expense Adjustments/Eliminations (GAAP),” using Object T with the appropriate sub-object and credits GL Code 3225 “Revenue Adjustments/Eliminations (GAAP)” with the appropriate revenue source code. Only in the case of GL Code 6525 transfers is there no corresponding Object T offset. Refer to Subsection 85.95.50.c for an illustrative entry.
Non-budgeted proprietary fund type accounts
For non-budgeted proprietary fund type accounts (excluding accounts 443 and 505 which are subject to (1) above), reimbursements are not coded as credits to expenses using object T. They are coded directly to revenue with appropriate revenue source codes. Refer to Subsection 85.95.50.d for an illustrative entry.
Interagency reimbursements (Object S) - All transactions between state agencies are to be properly accounted for as prescribed in RCW Chapter 39.34.
The following procedures are to be followed in those instances where a budgeted account or certain account used by higher education agencies - accounts 143, 145, 147, 148, 149, 443, and 505 which are included with budgeted accounts for purposes of this section - provides goods or services to another agency:
In accounting for interagency reimbursement transactions, the reimbursed agency is to credit expenditures/expenses using Object S - Interagency Reimbursements. The reimbursing agency is to account for expenditures for interagency materials supplied or services rendered as though they were purchased from an outside vendor. Refer to Subsection 85.95.60.a and b of this manual for illustrative entries.
Note: In budgeted accounts, interagency reimbursements are not to be recorded as revenue or as recovery of current appropriation expenditures using Revenue Source Code 0902 "Recoveries of Current Expenditure Authority Expenditures." Refer to Subsection 85.95.60.a and b for illustrative entries.
The amounts billed to other agencies and uncollected at the end of the month and work in process costs not billed at the end of the month are to be recorded as a credit to the appropriate GL code series 65XX "Expenditures/Expenses" with object S and a debit to GL code 1354 "Due from Other Agencies."
For GAAP reporting purposes, payments to budgeted proprietary fund type accounts should be recorded as revenues with appropriate revenue source codes. However, as discussed above, interagency reimbursements to budgeted proprietary fund type accounts are recorded as credits to expense (object S). Therefore, an additional entry is necessary to adjust to proper GAAP accounting. The GAAP adjustment debits GL code 6525 "Expense Adjustments/Eliminations (GAAP)," using object S with the appropriate sub-object and credits GL code 3225 "Revenue Adjustments/Eliminations (GAAP)" with the appropriate revenue source code. Refer to Subsection 85.95.60.c for an illustrative entry.
For nonbudgeted proprietary fund type accounts (excluding accounts 443 and 505 which are subject to (1) above), interagency reimbursements are not coded as credits to expenses (object S). They are coded directly to revenue with appropriate revenue source codes. Refer to Subsection Subsection 85.95.60.d for an illustrative entry.
Agencies are to establish procedures to ensure timely, accurate, and cost effective payment of obligations to agencies. Refer to Subsection 85.36 for information on payment methods.
Special attention by all agencies is to be given to the following:
Due Dates - Dates for payments are established by the terms of contracts between the state agencies. If the contract is silent concerning terms or there is no written contract, the terms are net 30 days. The 30 days, or other terms, begin upon receipt of the goods or services or a properly completed invoice, whichever is later. Agency payments are to be made by the due date.
Combined Payments - The number of payments to an agency are to be kept to a minimum by processing the maximum number of invoices with a single payment.
Partial Payments - When agencies accept partial delivery of goods or services without reservation, prompt payment is to be made for the goods or services received upon receipt from the agency of a properly completed invoice or in accordance with contract terms covering the partial delivery.
Disputes - Prompt and proper notification to an agency of receipt of unsatisfactory goods or services or an incorrect invoice defers the due date. The due date is recalculated from the date the problem is corrected. Proper authorization is required when material changes are made.
Records - Billings are to reflect the cost of labor, material and overhead. Records are to be maintained by the vendor agency that provides complete cost billing information and also an audit trail for post auditing. Source documentation should be made available, upon request, for review by the billed agency.
When problems arise with the collection of interagency receivables, agencies are to follow the steps in Subsection 85.90.40.d.
Vendor agencies are not to request or require advances from receiving agencies unless the advance was approved in writing by the OFM Director or authorized designee (RCW 39.34.150).
Refer to Section 90.20 for additional requirements applicable to fiscal year end cutoff.
July 1, 2001
|Agency vendor payment revolving account charges|
Account 720 "Agency Vendor Payment Revolving Account" may be used by agencies (RCW 42.26), with the approval of OFM, for the payment of goods or services which are payable from monies other than those maintained in the Office of the State Treasurer.
Use of Account 720 by agencies is to be authorized in writing by the Director of OFM or authorized designee.
Amounts disbursed from Account 720 must be from amounts previously deposited by the agency using the account. These deposits must be from local accounts which are properly chargeable with the disbursement. Amounts to cover disbursements must be deposited prior to actual disbursement. Refer to Subsection 85.95.70 for illustrative entries.
All amounts accruing to Account 720 as a result of the cancellation of warrants are to be re-deposited in the agency's appropriate local account.
Only the following accounts are to be maintained in the general ledger of Account 720: GL Codes 4310 "Current Treasury Cash Activity (OST Only)," 4325 "Beginning Treasury Cash Balance - Agency Funds," 5199 "Other Liabilities," and the 71XX "In-Process" Series. Subsidiary ledgers are not required. Refer to Subsection 85.95.70 for illustrative entries.