TRANXACT.AI Помощь

Public-sector ERP: FASRG, deferred pay, GASB 87/96, risk and claims, SchoolSpring

English only. Menu paths are the real ones.

English only. Menu paths are the real ones.

Chart standards: FASRG and other validations

Where: Accounting › Ledger › General Ledger. The screens are Chart Standards, Chart Segments, Chart Code Lists, Chart Edits, Chart Validation Findings and PEIMS Financial Extract.

A chart standard is a published account-code structure together with its edits. Four standards ship with every company, and all four start switched off:

| Standard | What it is | |---|---| | FASRG | The Texas Financial Accountability System Resource Guide. Fund 3, function 2, object 4, sub-object 2, organization 3, fiscal year 1, program intent 2 and local option 3, for example 199-11-6119-00-001-7-11-000. | | GASB34 | Every line carries a fund, the fund's type is a GASB 34/54 type, and proprietary funds capitalise their assets. | | UG200 | Uniform Guidance (2 CFR 200). On a federal award (a grant with an Assistance Listing number), the selected unallowable costs are refused: alcohol, bad debts, donations, entertainment, fines, fundraising and lobbying. A purchase order or invoice dated outside the award's period of performance is also refused. | | OK-OCAS | Oklahoma's chart. It is a second-state example, showing that the framework is not shaped only for Texas. |

How the account code is read. Nothing is typed twice. Each segment is read from a line the product already has:

  • fund: the line's fund (Fund Accounting › Funds);
  • function and program intent: the line's function and program;
  • object and sub-object: characters of the GL account number;
  • organization: the cost center;
  • fiscal year: the fiscal year the date falls in, named by the year it ends in. With a September start, 15 November 2026 is fiscal year 2027, digit 7.

Where the edits run. The edits run on these lines:

  • journal lines, and so on everything that posts, including the payroll distribution;
  • supplier invoice lines;
  • customer invoice lines;
  • purchase order lines;
  • budget lines.

The standard's Runs on field says which of these apply.

A purchase order line has no GL account, so edits about the object are not asked of it. When a standard is switched on, its When an edit fails setting decides what happens:

  • Refuse the line: errors refuse the line, showing the edit's message and citation.
  • Save it and list a finding: the line is saved, and the finding is listed under Chart Validation Findings.

Before switching FASRG on:

  1. Load TEA's full code lists. The lists shipped are an abridged sample. Use Chart Standards › Load code list and paste a CSV in the form value,name[,category,valid_from_fy,valid_to_fy], one segment at a time.
  2. Try lines with Test a line. It shows the account code a line would carry and every edit it would fail. It writes nothing.

Adding another state's chart or a funder's rules needs no code:

  1. Add a chart standard.
  2. Add its segments and say where each is read from.
  3. Load its code lists.
  4. Write its edits. The edit types are; required; on the code list; pattern; combination (when one segment matches, another must match); exclusion; allowability on a federal award; grant period.

PEIMS Financial Extract. This is the PEIMS Mid-Year financial picture: actuals (posted lines) and budget (budget lines of non-draft budgets) by the FASRG account code. It comes as the Ed-Fi LocalAccount, LocalActual and LocalBudget records that TSDS takes, or as CSV (add ?format=csv).

  • Revenue is reported as a positive amount.
  • A line missing a segment is listed under "incomplete" and is not guessed into the extract.
  • Sending to the TSDS ODS needs the district's TEA credentials.

Who:

  • The Financial Controller keeps the standards.
  • The Group Accountant works the findings.
  • The CPA reads the standards and the extract.

Deferred pay

Where: HRMS › Payroll › Pay Setup › Deferred Pay Contracts, and HRMS › Payroll › Pay Processing › Deferred Pay Accrual and Deferred Pay — TRS Report.

A deferred pay contract covers a 10- or 11-month contract paid over 12. The payroll already pays a salaried person their annual salary in equal instalments. The contract keeps what is earned against what is paid.

Earned and paid:

  • Earned is the salary multiplied by the share of the work period's working days that have passed.
  • Paid is the salary lines of the approved, posted or paid runs dated inside the pay year.

Actions on a contract:

| Action | What it does | |---|---| | Activate | Makes a draft contract active. It warns if the employee record's salary differs from the contract's. | | Earned and paid | Shows earned against paid, and what is owed, as of today. | | Summer payout | Pays the summer instalments as one lump sum (earning code DEFLUMP) on the next open pay period after the work period. The salary is then not paid again for the rest of the pay year. | | Separation | For a person who leaves mid-year. Whatever was earned and not yet paid is put on the final pay as a lump sum. If more was paid than earned, the overpayment is stated and never deducted automatically. |

Run the accrual works out earned less paid for every active contract and posts the change in the liability:

  • an increase is Dr salaries and wages, Cr accrued wages payable (2161 in the FASRG chart);
  • a decrease is the reverse;
  • run again on the same day, it posts nothing.

TRS (Texas). A contract can be marked TRS-reportable, on the paid or earned basis. The TRS report lists the amounts paid by month.

Who:

  • The Payroll Administrator keeps the contracts and runs the accrual.
  • The Payroll Auditor and the Financial Controller read them.

GASB 87 leases and GASB 96 subscriptions

Where:

  • Leases stay in one register, under Accounting › Revenue & Projects › Lease Accounting › Leases.
  • Accounting › Ledger › Assets gains Subscriptions (SBITA) and GASB Lease Disclosures.

Setting up. Set an accounting principle's Lease standard to gasb87 (Accounting › Ledger › Ledgers & Principles), and give a lease that principle.

GASB 87, lessee:

  • There is one model. Every lease that is not short-term becomes a lease liability and an intangible right-to-use asset, amortised straight-line, with interest on the liability.
  • There is no low-value exemption.
  • Short-term means the maximum possible term, with every option counted, is 12 months or less.

GASB 87, lessor:

  • The asset let stays on the books.
  • At commencement: Dr lease receivable, Cr deferred inflow of resources.
  • Each period, the lease run earns interest revenue on the receivable and releases the deferred inflow to lease revenue straight-line.
  • This covers the district's real-estate holdings, the properties under Lease Accounting › Real Estate.

GASB 96, subscriptions:

  • Enter the subscription as a lease of type Subscription (SBITA, GASB 96).
  • Its asset is the liability plus the implementation costs (the capitalisable initial implementation stage).
  • It posts to the subscription asset and subscription liability accounts. If those are not set, it posts to the right-of-use asset and lease liability accounts.

GASB Lease Disclosures gives principal and interest for each of the next five fiscal years, then in five-year bands, separately for lessee leases, lessor leases and subscriptions. The fiscal year's start month is set on the screen (fyStartMonth).

Who: the Lease Accountant, the Asset Accountant and the Financial Controller.

Risk management and claims

Where: Accounting › Close & Controls › Risk & Claims. The screens are Insurance Policies, Insurance Coverages, Incidents, Claims, Claim Transactions, Certificates of Insurance and Risk Register.

Policies:

  • the line, the insurer (a supplier, or a name) and the broker;
  • the period, the premium and the limits;
  • the deductible or self-insured retention;
  • the coverages inside the policy.

Incidents cover property damage, liability, vehicles, and a visitor's or a student's injury. An employee hurt at work is an HRMS safety incident (HRMS › Compliance › Health & Safety). A workers' compensation claim links to that safety incident, and must name the employee or the safety incident.

Claims. Every movement on a claim posts a journal:

| Action | What it posts | |---|---| | Set reserve | Dr claims expense, Cr claims liability (or the reverse when the reserve is lowered). | | Record payment | Dr claims liability, Cr cash. A payment beyond the reserve first raises the reserve, so the liability never goes negative. | | Record recovery | Dr cash, Cr insurance recoveries. The recovery can be from the insurer, subrogation, salvage or other. | | Close claim | Releases any reserve left. Nothing more can be recorded against a closed claim. |

Certificates of Insurance are supplier certifications (Supply Chain › Supplier Management). They carry:

  • the line, the insurer and the limit;
  • whether the company is an additional insured.

The screen lists them with their expiry: expired, expiring within 30 days, or current.

Risk Register:

  • likelihood × impact, before and after controls;
  • the treatment: avoid, reduce, transfer or accept;
  • the owner;
  • the policy that transfers the risk, where one does.

Who:

  • The Risk Manager role is new and keeps all of it.
  • The Financial Controller also keeps it.
  • The Finance Risk Analyst keeps the register and reads claims and policies.
  • Accounts Payable reads certificates of insurance.

SchoolSpring connector

Where: Platform › Connectivity › Integration.

  • The connector SchoolSpring educator hiring is in the Connector Catalog.
  • A connection to it carries the district's endpoint and API key.
  • SchoolSpring Runs lists what each run did.

Actions on a SchoolSpring connection:

  • Sync with SchoolSpring runs three flows; Postings out: HRMS job postings on the job board channel named SchoolSpring. SchoolSpring's reference is kept on the posting; Applicants in: each applicant becomes an HRMS candidate, matched by e-mail where one exists, with an application on the posting; Hires in: a hire marks the application hired.
  • Import SchoolSpring file reads applicants or hires from a CSV, as an SFTP drop delivers it; applicants: applicant_id,first_name,last_name,email,phone,posting_ref,applied_on,certification; hires: applicant_id,email,hired_on

Transport. The connection's configuration says which transport to use:

| Transport | When to use it | |---|---| | api | The district's SchoolSpring API. The paths are configuration; confirm them with PowerSchool. | | file | A CSV export, read by Import SchoolSpring file. | | mock | A sandbox connection only. A fixed test SchoolSpring answers, so the flows can be tried before the district has credentials. |

The connector fails closed: a live connection with no API key, or the mock on a non-sandbox connection, is refused with what to set up.

A second sync makes no duplicates.

Who:

  • The Integration Engineer runs it.
  • The HR Recruiter works the applications in HRMS › Hiring.

<!-- from help-fvfin.md -→