Difference between revisions of "How to configure InfiniteERP high level?"
(→initial setup) |
|||
Line 1: | Line 1: | ||
== initial setup == | == initial setup == | ||
− | + | # initial client setup | |
# create new organization type (optional, required when you need organization that represent as a business unit) | # create new organization type (optional, required when you need organization that represent as a business unit) | ||
# initial organization setup for group company | # initial organization setup for group company | ||
Line 10: | Line 10: | ||
# apply fiscal calendar on legal entity organization | # apply fiscal calendar on legal entity organization | ||
# set as ready on group company organization (thick cascade checkbox) | # set as ready on group company organization (thick cascade checkbox) | ||
− | # | + | # |
+ | |||
== role == | == role == | ||
# create a role, pay more attention to manual field | # create a role, pay more attention to manual field |
Revision as of 20:15, 25 June 2024
Contents
- 1 initial setup
- 2 role
- 3 user
- 4 financial account master data
- 5 tax master data
- 6 product master data
- 7 master business partner
- 8 master warehouse
- 9 transaksi pembelian (requisition –> purchase order –> goods shipment –> purchase invoice –> payment out)
- 10 transaksi penjualan (sales order –> goods shipment –> sales invoice –> payment in)
- 11 stock opname
- 12 rekonsiliasi bank
initial setup
- initial client setup
- create new organization type (optional, required when you need organization that represent as a business unit)
- initial organization setup for group company
- initial organization setup for legal entity (COA included)
- initial organization setup for company branch
- create fiscal calendar for each legal entity
- create fiscal year for each created fiscal calendar
- generate period for each fiscal year
- apply fiscal calendar on legal entity organization
- set as ready on group company organization (thick cascade checkbox)
role
- create a role, pay more attention to manual field
- create record on organization access tab, window access tab, process definition tab, and other tab as required
user
- create new user
- assign user role to created user account
financial account master data
- make sure all COA for bank account already exists
- make sure all COA for bank in transit (temporary account) already exists
- create a new payment method
- create a financial account (header)
- assign payment method to financial account (financial account || payment method)
- verify accounting configuration for this financial account
tax master data
- makse sure all COA for taxation already exists
- make a new tax category
- make a new buat business partner tax category
- make a new tax rate, pay attention to field below: tax category, country, and business partner tax category.
- verify accounting configuration for this tax rate
product master data
- pastikan COA expense sudah lengkap
- pastikan COA revenues sudah lengkap
- pastikan COA CoGS sudah lengkap
- pastikan COA persediaan sudah lengkap
- pastikan COA selisih harga pembelian sudah lengkap
- buat master product category
- pastikan seting akuntansi pada product category sudah tepat
- buat master produk, hati-hati pada field tax category dan product category
master business partner
- buat payment term
- pastikan COA hutang sudah lengkap
- pastikan COA piutang sudah lengkap
- pastikan COA barang diterima dimuka sudah lengkap
- buat master business partner category
- buat master business partner
- pada sub tab location/address isikan alamat business partner
- pada sub tab customer (jika ini adalah BP customer), isikan default payment term dan payment method
- pada sub tab vendor (jika ini adalah BP vendor), isikan default payment term dan payment method
master warehouse
- pastikan COA penyesuaian persediaan sudah lengkap
- buat warehouse
- buat storage bin
- registrasi warehouse pada window organization sub tab warehouse
- buat costing rule
- click validate pada costing rule
transaksi pembelian (requisition –> purchase order –> goods shipment –> purchase invoice –> payment out)
- buat requisition (optional)
- complete requisition (wajib jika requisition digunakan)
- konversi requisition menjadi PO melalui form requisition to order (wajib jika requisition digunakan)
- buat PO (optional, namun jika pakai requisition, maka PO otomatis terbentuk dari requisition to order form)
- complete PO (wajib jika PO digunakan, namun PO otomatis complete jika via requisition to order form jika requisition digunakan)
- buat goods receipt, create lines from, pilih dari PO (wajib jika PO berisi stocked product)
- complete goods receipt (wajib jika goods receipt digunakan)
- terbentuk jurnal otomatis untuk pengakuan persediaan
- buat purchase invoice, create lines form, pilih dari GR (wajib jika goods receipt digunakan, harus buat lines manual jika purchase invoice berdiri sendiri – tidak berdasar PO/GR)
- complete purchase invoice (wajib)
- terbentuk jurnal otomatis untuk pengakuan hutang
- terbentuk dokumen matched invoice (jika ada link dari PI ke GR)
- terbentuk jurnal otomatis untuk menyesuaikan selisih harga dan membalik barang diterima dimuka (ada jika terbentuk matched invoice)
- buat payment out, tarik purchase invoice yang akan dibayar
- terbentuk dokumen finalcial account || transaction secara otomatis
- terbentuk jurnal yang menutup hutang dan mengurangi kas secara otomatis (berdasarkan financial account || transaction)
transaksi penjualan (sales order –> goods shipment –> sales invoice –> payment in)
- buat sales order (optional)
- complete sales order (wajib jika SO digunakan)
- buat goods shipment, create lines from, pilih dari SO (wajib jika SO berisi stocked product)
- complete goods shipment (wajib jika goods shipment digunakan)
- terbentuk jurnal otomatis untuk pengakuan CoGS
- buat sales invoice, create lines form, pilih dari GS (wajib jika goods shipment digunakan, harus buat lines manual jika sales invoice berdiri sendiri – tidak berdasar SO/GS)
- complete sales invoice (wajib)
- terbentuk jurnal otomatis untuk pengakuan pendapatan
- buat payment in, tarik sales invoice yang diterima pelunasannya
- terbentuk dokumen finalcial account || transaction secara otomatis
- terbentuk jurnal yang menutup piutang dan menambah kas secara otomatis (berdasarkan financial account || transaction)
stock opname
- pastikan table physical inventory di window general ledger configuration sub tab active table, sudah ada.
- buat physical inventory
- buat physical inventory list
- lakukan perhitungan fisik dan catat hasilnya di field quantity count
- complete physical inventory, saldo persediaan akan diupdate sesuai dengan quantity count
- terbentuk jurnal penyesuaian persediaan pada persedian secara otomatis
rekonsiliasi bank
- buka window financial account
- klik button reconcile
- masukkan tanggal rekonsiliasi
- masukkan saldo akhir bank per taggal rekonsiliasi
- centang transaksi bank yang sudah tertera di bank statement
- jika sisa sudah nol, maka klik reconcile
- jika tidak, klik tombol save.
- buat transaksi bank untuk pending transaction berdasar bank statement
- ulangi langkah 2 tapi lewati langkah 3 dan 4 sehingga langsung ke langkah 5
- transaksi bank (financial account transaction) akan hilang dan pindah ke sub tab tab reconciliation