회계 › Finance Configuration
Finance Configuration
Company-wide finance switches. AP match defaults apply where neither the item nor the supplier says otherwise (empty keeps today's 2% and three-way). Item accounts and strict posting roles are off until you switch them on.
어디에서 찾을 수 있나요?
- 기준 치수: 회계
- 그룹: Close & Controls
- 부분: Finance Configuration
- 화면: Finance Configuration
콘솔에 표시된 주소: /accounting/fin-config-settings
목록 · 8 컬럼 · 12 그 양식의 필드
목록이 보여주는 것
다음은 목록의 열이며, 표시된 순서대로 나열되어 있습니다. 각 열은 정렬, 필터링, 숨기기 또는 내보내기가 가능합니다.
| 열 | 친절한 | 필드 이름 |
|---|---|---|
| AP match | 상태 | ap_match_option |
| 가격 허용 오차 % | 숫자 | ap_price_tolerance_pct |
| 수량 허용 오차 % | 숫자 | ap_quantity_tolerance_pct |
| Item accounts | 예 또는 아니오 | honour_item_accounts |
| Posting roles | 상태 | role_resolution |
| Non-PO invoices approved above | 양 | ap_non_po_approval_threshold |
| Close checklist required | 예 또는 아니오 | require_close_checklist |
| Labor in the GL | 상태 | labour_gl_mode |
양식
레코드를 생성할 때 요청되는 정보입니다. 필수 필드는 표시되어 있으며, 구성 목록에서 선택하는 경우 관리자는 릴리스 없이도 기능을 확장할 수 있습니다.
| 필드 | 유형 | 선택 | 메모 |
|---|---|---|---|
| Supplier invoice match | 선택 | Three-way (order, receipt, invoice) - today, Two-way (order and invoice), Four-way (adds the inspection), No match | What a supplier invoice on an order is matched against. An item or supplier set to anything but three-way keeps its own choice. |
| 가격 허용 오차(%) | 숫자 | How far an invoice may exceed the order value and still match. Empty: 2%. An item or supplier tolerance wins. | |
| 수량 허용 오차(%) | 숫자 | How far an invoice may exceed what was received and still match. Empty: 2%. | |
| Approve supplier invoices without a purchase order above | 숫자 | In the company currency. A supplier invoice with no purchase order worth more than this is sent for approval when it is posted, and posts only once approved. Who approves is set under Platform > Configuration > Approval Routes, document type "Supplier invoice without a purchase order" (by amount, unit, supplier or currency). Empty: off, as today. 0: every such invoice. Invoices on a purchase order are matched as before. | |
| Require the close checklist before closing a period | 예 또는 아니오 | On (the default): a period is not closed -- from Fiscal Periods, by finishing another close of the period, or by closing the general ledger under Period Close by Module -- while its Financial Close has blocking tasks outstanding or failed reconciliation checks. Forcing past it needs the Force Period Close right and a written reason, and is recorded. A period with no Financial Close is not held. Off: periods close as they did before. | |
| Labor from approved time in the general ledger | 선택 | None: project cost only, Reclass: move it from payroll expense to the project, Cost: a full labor journal against a clearing account | Approved project hours are always project cost. Reclass also posts a journal moving the same amount out of the payroll expense account into the project account, on the cost center, grant, fund and program of the hours -- for companies whose payroll runs here. Cost posts the project account against an accrued payroll / labor clearing account -- for companies whose payroll is run elsewhere. Either way a correction posts only the difference, and when payroll is posted its true-up is journaled the same way. Approval is refused in a closed period. |
| Project cost / WIP account | 선택 | 기존 기록에서 조회함 | Needed for reclass and cost: the account the labor is charged to. |
| Payroll expense account | 선택 | 기존 기록에서 조회함 | What a reclass moves the labor out of. Empty: the account with the wages posting role, which payroll posts to. |
| Accrued payroll / labor clearing account | 선택 | 기존 기록에서 조회함 | What a full labor journal is credited to. |
| Post to the item's own accounts | 예 또는 아니오 | Goods receipts, deliveries and invoices use the inventory, cost of sales and revenue accounts on the item (Item Costing), then the item-group matrix, then the company roles. Off: roles only. | |
| Posting roles | 선택 | Tagged account, else demo number or name (today), Strict: tagged account or Account Determination only | Strict never guesses an account from a number or a name: an unset role refuses the posting and names the role. Use Posting Roles > Lock mapping to move over without changing a single answer. |
| 메모 | 긴 글 |
여기에 적용되는 규칙
이 화면의 모든 항목은 자체 규칙이 아닌 플랫폼 규칙을 따릅니다. 사용하기 전에 알아두면 좋은 규칙은 다음과 같습니다.
- 목록 좁히기 — 검색, 조건 설정, 정렬, 합계, 내보내기 및 저장된 보기 기능.
- 무엇이 바뀔 수 있을까요? — 음반을 수정할 수 없는 다섯 가지 사유.
- 회사 및 사업부 — 이 목록 위에 있는 스위처가 무엇을 하고 있는지.
- 레코드 생성 — 필수 입력 항목, 선택 항목의 출처 및 개수 할당 방식.
- 스프레드시트 가져오기 — 이 화면은 하나의 입력을 받으며, 타이핑할 때와 동일한 규칙을 따릅니다.